Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
claude-code-workflow
description
Claude Code AI-assisted development workflow. Activate when discussing Claude Code usage, AI-assisted coding, prompting strategies, or Claude Code-specific patterns.
location
user
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Claude Code Workflow
Guidelines for effective AI-assisted development with Claude Code.
Task Value Matrix
Value
Task Type
Example
High
Boilerplate generation
CRUD endpoints, test scaffolding
High
Refactoring
Extract function, rename across files
High
Documentation
Docstrings, README updates
Medium
Bug investigation
Error analysis, log interpretation
Medium
Code review
Pattern suggestions, security review
Low
Novel architecture
Requires deep domain knowledge
Low
Ambiguous requirements
Needs human clarification
Workflow Patterns
Explore-Plan-Code-Commit (EPCC)
The RECOMMENDED workflow for most development tasks:
Explore: Use Glob, Grep, Read to understand existing code
MUST understand context before making changes
SHOULD identify related files and dependencies
MAY use subagents for parallel exploration
Plan: Outline changes before implementation
SHOULD create TodoWrite items for multi-step tasks
MUST validate plan covers edge cases
Code: Implement changes incrementally
MUST run tests after each significant change
SHOULD use Edit over Write for existing files
SHALL NOT introduce breaking changes without tests
Commit: Create logical, atomic commits
MUST follow semantic commit conventions
SHALL NOT commit secrets or credentials
Test-Driven Development with AI
1. Write failing test → 2. Implement minimum to pass → 3. Refactor → 4. Repeat
MUST run tests between each step
SHOULD use targeted test execution during development
Spike-Then-Implement
For uncertain implementations: Create throwaway spike, validate, delete, implement properly with tests.
Context Management
Efficient Prompting
MUST: Provide specific file paths, include error messages verbatim, state expected vs actual behavior
SHOULD: Reference previous context, specify output format, include constraints upfront
SHOULD NOT: Repeat information in context, include unnecessary background, ask multiple unrelated questions
