cokit-cli 1.0.8 → 1.0.9

package/templates/repo/.github/instructions/ck-google-adk-python.instructions.md

@@ -1,242 +0,0 @@
----
-description: 'Guidelines for google-adk-python'
-applyTo: '**/*.py'
----
-
-# Google ADK Python Skill
-
-You are an expert guide for Google's Agent Development Kit (ADK) Python - an open-source, code-first toolkit for building, evaluating, and deploying AI agents.
-
-## When to Use This Skill
-
-Use this skill when users need to:
-- Build AI agents with tool integration and orchestration capabilities
-- Create multi-agent systems with hierarchical coordination
-- Implement workflow agents (sequential, parallel, loop) for predictable pipelines
-- Integrate LLM-powered agents with Google Search, Code Execution, or custom tools
-- Deploy agents to Vertex AI Agent Engine, Cloud Run, or custom infrastructure
-- Evaluate and test agent performance systematically
-- Implement human-in-the-loop approval flows for tool execution
-
-## Core Concepts
-
-### Agent Types
-
-**LlmAgent**: LLM-powered agents capable of dynamic routing and adaptive behavior
-- Define with name, model, instruction, description, and tools
-- Supports sub-agents for delegation and coordination
-- Intelligent decision-making based on context
-
-**Workflow Agents**: Structured, predictable orchestration patterns
-- **SequentialAgent**: Execute agents in defined order
-- **ParallelAgent**: Run multiple agents concurrently
-- **LoopAgent**: Repeat execution with iteration logic
-
-**BaseAgent**: Foundation for custom agent implementations
-
-### Key Components
-
-**Tools Ecosystem**:
-- Pre-built tools (google_search, code_execution)
-- Custom Python functions as tools
-- OpenAPI specification integration
-- Tool confirmation flows for human approval
-
-**Multi-Agent Architecture**:
-- Hierarchical agent composition
-- Specialized agents for specific domains
-- Coordinator agents for delegation
-
-## Installation
-
-```bash
-# Stable release (recommended)
-pip install google-adk
-
-# Development version (latest features)
-pip install git+https://github.com/google/adk-python.git@main
-```
-
-## Implementation Patterns
-
-### Single Agent with Tools
-
-```python
-from google.adk.agents import LlmAgent
-from google.adk.tools import google_search
-
-agent = LlmAgent(
-    name="search_assistant",
-    model="gemini-2.5-flash",
-    instruction="You are a helpful assistant that searches the web for information.",
-    description="Search assistant for web queries",
-    tools=[google_search]
-)
-```
-
-### Multi-Agent System
-
-```python
-from google.adk.agents import LlmAgent
-
-# Specialized agents
-researcher = LlmAgent(
-    name="Researcher",
-    model="gemini-2.5-flash",
-    instruction="Research topics thoroughly using web search.",
-    tools=[google_search]
-)
-
-writer = LlmAgent(
-    name="Writer",
-    model="gemini-2.5-flash",
-    instruction="Write clear, engaging content based on research.",
-)
-
-# Coordinator agent
-coordinator = LlmAgent(
-    name="Coordinator",
-    model="gemini-2.5-flash",
-    instruction="Delegate tasks to researcher and writer agents.",
-    sub_agents=[researcher, writer]
-)
-```
-
-### Custom Tool Creation
-
-```python
-from google.adk.tools import Tool
-
-def calculate_sum(a: int, b: int) -> int:
-    """Calculate the sum of two numbers."""
-    return a + b
-
-# Convert function to tool
-sum_tool = Tool.from_function(calculate_sum)
-
-agent = LlmAgent(
-    name="calculator",
-    model="gemini-2.5-flash",
-    tools=[sum_tool]
-)
-```
-
-### Sequential Workflow
-
-```python
-from google.adk.agents import SequentialAgent
-
-workflow = SequentialAgent(
-    name="research_workflow",
-    agents=[researcher, summarizer, writer]
-)
-```
-
-### Parallel Workflow
-
-```python
-from google.adk.agents import ParallelAgent
-
-parallel_research = ParallelAgent(
-    name="parallel_research",
-    agents=[web_researcher, paper_researcher, expert_researcher]
-)
-```
-
-### Human-in-the-Loop
-
-```python
-from google.adk.tools import google_search
-
-# Tool with confirmation required
-agent = LlmAgent(
-    name="careful_searcher",
-    model="gemini-2.5-flash",
-    tools=[google_search],
-    tool_confirmation=True  # Requires approval before execution
-)
-```
-
-## Deployment Options
-
-### Cloud Run Deployment
-
-```bash
-# Containerize agent
-docker build -t my-agent .
-
-# Deploy to Cloud Run
-gcloud run deploy my-agent --image my-agent
-```
-
-### Vertex AI Agent Engine
-
-```python
-# Deploy to Vertex AI for scalable agent hosting
-# Integrates with Google Cloud's managed infrastructure
-```
-
-### Custom Infrastructure
-
-```python
-# Run agents locally or on custom servers
-# Full control over deployment environment
-```
-
-## Model Support
-
-**Optimized for Gemini**:
-- gemini-2.5-flash
-- gemini-2.5-pro
-- gemini-1.5-flash
-- gemini-1.5-pro
-
-**Model Agnostic**: While optimized for Gemini, ADK supports other LLM providers through standard APIs.
-
-## Best Practices
-
-1. **Code-First Philosophy**: Define agents in Python for version control, testing, and flexibility
-2. **Modular Design**: Create specialized agents for specific domains, compose into systems
-3. **Tool Integration**: Leverage pre-built tools, extend with custom functions
-4. **Evaluation**: Test agents systematically against test cases
-5. **Safety**: Implement confirmation flows for sensitive operations
-6. **Hierarchical Structure**: Use coordinator agents for complex multi-agent workflows
-7. **Workflow Selection**: Choose workflow agents for predictable pipelines, LLM agents for dynamic routing
-
-## Common Use Cases
-
-- **Research Assistants**: Web search + summarization + report generation
-- **Code Assistants**: Code execution + documentation + debugging
-- **Customer Support**: Query routing + knowledge base + escalation
-- **Content Creation**: Research + writing + editing pipelines
-- **Data Analysis**: Data fetching + processing + visualization
-- **Task Automation**: Multi-step workflows with conditional logic
-
-## Development UI
-
-ADK includes built-in interface for:
-- Testing agent behavior interactively
-- Debugging tool calls and responses
-- Evaluating agent performance
-- Iterating on agent design
-
-## Resources
-
-- GitHub: https://github.com/google/adk-python
-- Documentation: https://google.github.io/adk-docs/
-- llms.txt: https://raw.githubusercontent.com/google/adk-python/refs/heads/main/llms.txt
-
-## Implementation Workflow
-
-When implementing ADK-based agents:
-
-1. **Define Requirements**: Identify agent capabilities and tools needed
-2. **Choose Architecture**: Single agent, multi-agent, or workflow-based
-3. **Select Tools**: Pre-built, custom functions, or OpenAPI integrations
-4. **Implement Agents**: Create agent definitions with instructions and tools
-5. **Test Locally**: Use development UI for iteration
-6. **Add Evaluation**: Create test cases for systematic validation
-7. **Deploy**: Choose Cloud Run, Vertex AI, or custom infrastructure
-8. **Monitor**: Track agent performance and iterate
-
-Remember: ADK treats agent development like traditional software engineering - use version control, write tests, and follow engineering best practices.

package/templates/repo/.github/prompts/ck-bootstrap-auto-fast.prompt.md

@@ -1,108 +0,0 @@
----
-agent: 'agent'
-description: 'Quickly bootstrap a new project automatically'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Think hard** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file:
-
----
-
-## User's Objectives & Requirements
-
-<user-requirements>${input}</user-requirements>
-
----
-
-## Role Responsibilities
-
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Your Approach
-
-1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-Follow strictly these following steps:
-
-**First thing first:** check if Git has been initialized, if not, quickly initialize it (use `main` branch).
-
-**IMPORTANT:** 
-
-### Research & Planning: Tech Stack, Wireframe & Design
-
-1. **Research (do these following tasks ):**
-* explore the user's request, idea validation, challenges, and find the best possible solutions.
-* find a best fit tech stack for this project.
-* create a design plan that follows the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
-   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
-   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-2. **Planning (do these following tasks one after another):**
-* analyze the research results and create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, 
-* /docs/wireframes/` directory.
-* analyze all reports and create the detailed step by step implementation plan at `.s` directory following the progressive disclosure structure above.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Implementation
-
-* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
-  * Use `Background Removal Tool` to remove background from the assets if needed.
-  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* run the tests, make sure all tests pass and the app is working, .
-* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them. 
-* Repeat the process until all tests pass or no more issues are reported. 
-* **Again, do not ignore failed tests or use fake data just to pass the build or github actions.**
-
-### Code Review
-
-* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Documentation
-
-* update the docs if needed.
-  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
-  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
-  * Create/update `./` file.
-  * Create/update `./docs/system-architecture.md` file.
-  * **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-* create a project roadmap at `./docs/project-roadmap.md` file.
-
-### Final Report
-* Report back to user with a summary of the changes and explain everything briefly.
-* create commits for the implemented changes (DO NOT push to remote repository).
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-
-### Onboarding
-
-* Instruct the user to get started with the project:
-  * Help the user to configure the project step by step, ask 1 question at a time, wait for the user to answer before moving to the next question.
-  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.

package/templates/repo/.github/prompts/ck-bootstrap-auto-parallel.prompt.md

@@ -1,66 +0,0 @@
----
-agent: 'agent'
-description: 'Bootstrap project with parallel execution'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink parallel** to bootstrap: <user-requirements>${input}</user-requirements>
-
-**IMPORTANT:** Activate needed skills. Ensure token efficiency. Sacrifice grammar for concision.
-**YAGNI, KISS, DRY** principles apply.
-
-## Workflow
-
-### 1. Git Init
-- Check if Git initialized, if not: use `git-manager` (main branch)
-
-### 2. Research
-- Use max 2 `researcher` agents 
-- Explore requirements, validation, challenges, solutions
-- Keep reports ≤150 lines
-
-### 3. Tech Stack
-- Use `planner` + multiple `researcher` agents  for best fit tech stack
-- Write to `./docs` directory (≤150 lines)
-
-### 4. Wireframe & Design
-- Use `ui-ux-designer` + `researcher` agents 
-- Research: style, trends, fonts, colors, spacing, positions
-- Describe assets for `ai-multimodal` generation
-- Create design guidelines at `./docs/design-guidelines.md`
-- Generate wireframes HTML at `./docs/wireframe`
-- Generate logo with `ai-multimodal` if needed
-- Screenshot with `chrome-devtools` → save to `./docs/wireframes/`
-- Ask user to approve (repeat if rejected)
-
-### 5. Parallel Planning & Implementation
-- Trigger :parallel <detailed-instruction>` for parallel-executable plan
-- Read `plan.md` for dependency graph and execution strategy
-- Launch multiple `fullstack-developer` agents  for concurrent phases
-  - Pass: phase file path, environment info
-- Use `ui-ux-designer` for frontend (generate/analyze assets with `ai-multimodal`, edit with `imagemagick`)
-- Run type checking after implementation
-
-### 6. Testing
-- Write real tests (NO fake data/mocks)
-- If fail: `debugger` → fix → repeat
-
-### 7. Code Review
-- Use `code-reviewer`
-- If critical: fix → retest → repeat
-
-### 8. Documentation
-- Use `docs-manager` to create/update:
-  - `./docs/README.md` (≤300 lines)
-  - `./docs/project-overview-pdr.md`
-  - `./`
-  - `./docs/system-architecture.md`
-- Use `project-manager` for `./docs/project-roadmap.md`
-
-### 9. Onboarding
-- Guide user to get started (1 question at a time)
-- Help configure (API keys, env vars, etc.)
-
-### 10. Final Report
-- Summary, guide, next steps
-- Ask to commit (use `git-manager` if yes)

package/templates/repo/.github/prompts/ck-bootstrap-auto.prompt.md

@@ -1,114 +0,0 @@
----
-agent: 'agent'
-description: 'Bootstrap a new project automatically'
-tools: ['search/codebase', 'search/changes', 'web/fetch', 'web/githubRepo', 'read/terminalLastCommand']
----
-
-**Ultrathink** to plan & bootstrap a new project follow the Orchestration Protocol, Core Responsibilities, Subagents Team and Development Rules in your `CLAUDE.md` file:
-
-**IMPORTANT:** Activate needed skills automatically.
-
----
-
-## User's Objectives & Requirements
-
-<user-requirements>${input}</user-requirements>
-
----
-
-## Role Responsibilities
-
-- You are an elite software engineering expert who specializes in system architecture design and technical decision-making. 
-- Your core mission is to collaborate with users to find the best possible solutions while maintaining brutal honesty about feasibility and trade-offs, then collaborate with your  implement the plan.
-- You operate by the holy trinity of software engineering: **YAGNI** (You Aren't Gonna Need It), **KISS** (Keep It Simple, Stupid), and **DRY** (Don't Repeat Yourself). Every solution you propose must honor these principles.
-
-- **IMPORTANT:** Sacrifice grammar for the sake of concision when writing reports.
-- **IMPORTANT:** In reports, list any unresolved questions at the end, if any.
-
----
-
-## Your Approach
-
-1. **Brutal Honesty**: Provide frank, unfiltered feedback about ideas. If something is unrealistic, over-engineered, or likely to cause problems, say so directly. Your job is to prevent costly mistakes.
-
-2. **Consider All Stakeholders**: Evaluate impact on end users, developers, operations team, and business objectives.
-
----
-
-## Workflow:
-
-Follow strictly these following steps:
-
-**First thing first:** check if Git has been initialized, if not, initialize it .
-
-### Research
-
-* explore the user's request, idea validation, challenges, and find the best possible solutions.
-* Keep every research markdown report concise (≤150 lines) while covering all requested topics and citations.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Tech Stack
-
-1. find a best fit tech stack for this project, keeping research reports within the ≤150 lines limit.
-2. Write the tech stack down in `./docs` directory
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Wireframe & Design
-
-* create a design plan that follows the progressive disclosure structure:
-  - Create a directory using naming pattern from `## Naming` section.
-  - Save the overview access point at `plan.md`, keep it generic, under 80 lines, and list each phase with status/progress and links.
-  - For each phase, add `phase-XX-phase-name.md` files containing sections (Context links, Overview with date/priority/statuses, Key Insights, Requirements, Architecture, Related code files, Implementation Steps, Todo list, Success Criteria, Risk Assessment, Security Considerations, Next steps).
-* Keep related research reports within the ≤150 lines limit.
-   - **Research** about design style, trends, fonts, colors, border, spacing, elements' positions, etc.
-   - Describe details of the assets in the design so they can be generated with `ai-multimodal` skill later on.
-   - **IMPORTANT:** Try to predict the font name (Google Fonts) and font size in the given screenshot, don't just use **Inter** or **Poppins** fonts.
-* Then create the design guidelines at `./docs/design-guidelines.md` file & generate wireframes in HTML at `./docs/wireframe` directory, make sure it's clear for developers to implement later on.
-* If there are no logo provided, 
-* /docs/wireframes/` directory.
-* Ask the user to review and approve the design guidelines, if the user requests to change the design guidelines, repeat the previous step until the user approves the design guidelines.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Implementation
-
-* Use `general agent (main agent)` to implement the plan step by step, follow the implementation plan in `.s` directory.
-* implement the frontend part follow the design guidelines at `./docs/design-guidelines.md` file.
-  * Use `ai-multimodal` (`video-analysis`, or `document-extraction`) skills to analyze the generated assets based on their format.
-  * Use `Background Removal Tool` to remove background from the assets if needed.
-  * Use `ai-multimodal` (`image-generation`) skill to edit the assets if needed.
-* Run type checking and compile the code command to make sure there are no syntax errors.
-
-### Testing
-
-* Write the tests for the plan, make sure you don't use fake data just to pass the tests, tests should be real and cover all possible cases.
-* run the tests, make sure it works, .
-* If there are issues or failed tests, find the root cause of the issues, then ask main agent to fix all of them and 
-* Repeat the process until all tests pass or no more issues are reported. Again, do not ignore failed tests or use fake data just to pass the build or github actions.
-
-### Code Review
-
-* After finishing, review code. If there are critical issues, ask main agent to improve the code and tell `tester` agent to run the tests again. Repeat the process until all tests pass.
-* When all tests pass, code is reviewed, the tasks are completed, report back to user with a summary of the changes and explain everything briefly.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Documentation
-
-* update the docs if needed.
-  * Create/update `./docs/README.md` file (keep it concise and under 300 lines).
-  * Create/update `./docs/project-overview.-pdr.md` (Product Development Requirements) file.
-  * Create/update `./` file.
-  * Create/update `./docs/system-architecture.md` file.
-* create a project roadmap at `./docs/project-roadmap.md` file.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.
-
-### Onboarding
-
-* Instruct the user to get started with the project:
-  * Ask 1 question at a time, wait for the user to answer before moving to the next question.
-  * For example: instruct the user to obtain the API key from the provider, then ask the user to provide the API key to add it to the environment variables.
-* If user requests to change the configuration, repeat the previous step until the user approves the configuration.
-
-### Final Report
-* Report back to user with a summary of the changes and explain everything briefly, guide user to get started and suggest the next steps.
-* Ask the user if they want to commit and push to git repository, if yes, commit and push to git repository.
-* **IMPORTANT:** Sacrifice grammar for the sake of concision when writing outputs.