Agent Skills › pass-with-high-score/blockads-android › cook

cook

GitHub

高自主性“厨师”技能，用于从零开始实现新功能。涵盖代码扫描、架构研究、技术规格制定及全栈实现，强调遵循项目规范和编写整洁代码。适用于用户要求实现特定功能或构建新模块的场景。

.agent/skills/cook/SKILL.md pass-with-high-score/blockads-android

Trigger Scenarios

用户说“cook this feature” 用户要求“implement X” 用户要求“build Y”

Install

npx skills add pass-with-high-score/blockads-android --skill cook -g -y

More Options

Non-standard path

npx skills add https://github.com/pass-with-high-score/blockads-android/tree/main/.agent/skills/cook -g -y

Use without installing

npx skills use pass-with-high-score/blockads-android@cook

指定 Agent (Claude Code)

npx skills add pass-with-high-score/blockads-android --skill cook -a claude-code -g -y

安装 repo 全部 skill

npx skills add pass-with-high-score/blockads-android --all -g -y

预览 repo 内 skill

npx skills add pass-with-high-score/blockads-android --list

SKILL.md

Frontmatter

{
    "name": "cook",
    "description": "High-autonomy \"chef\" for implementing new features from scratch. Handles code scanning, architectural research, technical specification, and full-stack implementation with a focus on \"clean code\" and project idiomatics. Use when the user says \"cook this feature\", \"implement X\", or \"build Y\"."
}

The "Cook" Workflow

This skill transforms a high-level feature request into a production-ready implementation through a structured "kitchen" process.

Phase 1: Preparation (Research & Scan)

Scan: Use grep_search and glob to find existing patterns, related components, and architectural precedents.
Analyze: Understand how data flows and how existing features are structured in this specific codebase.
Ingredients: Identify the "ingredients" needed (new classes, UI components, API endpoints, or database changes).

Phase 2: The Recipe (Clear Spec)

Draft Spec: Create a concise technical plan.
Check-in: Present the plan to the user.
Clarify: If anything is ambiguous (UI details, edge cases), ASK for confirmation before touching the stove.

Phase 3: Cooking (Implementation)

Atomic Commits: (Mental or actual if requested) Build the feature in logical, self-contained steps.
Idiomatic Code: Follow the project's established style (naming, patterns, libraries).
Clean Code: Prioritize readability, DRY principles, and proper error handling.

Phase 4: Taste Test (Verification)

Verify: Run the build (./gradlew assembleDebug) and relevant tests.
Cleanup: Remove any temporary debug logs, comments, or unused imports.

Phase 5: Serving (Final Review)

Report: Summarize what was built and how to test it.

Guardrails

Don't Over-Season: Stay within the scope of the requested feature.
Fresh Ingredients: Always use the latest project conventions found in GEMINI.md.
Safety First: Never proceed with high-impact architectural changes without an approved "Recipe".