- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill implementation-approach -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill implementation-approach -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill implementation-approach -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add shinpr/ai-coding-project-boilerplate --skill implementation-approach -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/shinpr/ai-coding-project-boilerplate/tree/HEAD/.claude/skills-en/implementation-approachDo publicador
Core Question: "What does the existing implementation look like?"
Architecture Analysis: Responsibility separation, data flow, dependencies, technical debt
Implementation Quality Assessment: Code quality, test coverage, performance, security
Historical Context Understanding: Current form rationale, past decision validity, constraint changes, requirement evolution
Stop when another current-state fact cannot change responsibility, reuse, option validity, total complexity, a contract, or verification.
Completion evidence: inspected paths, observed architecture/data-flow facts, known constraints, inferred historical rationale labeled as inferred, and unknowns that could change strategy selection.
Transition: proceed when every strategy-relevant claim is observed, explicitly inferred with evidence, or recorded as unknown.
Core Question: "What is the smallest design that delivers the current required outcome, and what evidence forces each addition beyond it?"
Complete these steps in order before exploring implementation strategies:
Candidate paths and rejected additions remain active analysis. The durable output is the Selected Design: the complete chosen path plus evidence for each added design surface and the condition that fails when it is removed. Only an accepted ADR may retain alternatives as decision history. During implementation, use the same convergence check without producing a separate artifact.
Completion evidence: one complete Selected Design; every added design surface names its current evidence, why lower-surface resolutions fail, and its subtraction result.
Transition: proceed when every supporting claim is observed, explicitly inferred with evidence, or recorded as unknown; route an unknown that blocks the next step as an exact evidence prerequisite. User interaction is required only when the unknown requires changing the outcome, desired-future requirements, or non-goals, or authorizing an irreversible action.
Core Question: "When determining before -> after, what implementation patterns or strategies should be referenced?"
Direct Strategy: The smallest repository-supported strategy that delivers the Selected Design within the hard constraints
Research Order: repository patterns first; then official documentation for the resolved dependency version; then maintained OSS implementations; use literature/blogs only as supplements labeled non-authoritative
Use a pattern only when its named migration or dependency problem exists in the repository.
Legacy Handling Strategies:
New Development Strategies:
Integration/Migration Strategies:
Completion evidence: the direct strategy mapped to the observed constraints it satisfies and the constraints it leaves unresolved, plus an alternative only when it would materially change risk, compatibility, rollout, or the early verification point.
Transition: proceed when the direct strategy and any retained alternative are comparable against the same constraint set.
Core Question: "What risks arise when applying this to the existing implementation, and which control measurably reduces likelihood or impact while preserving verification and rollback?"
Evaluate only risk categories for which current evidence can change the strategy, public contract, rollout, rollback, or verification boundary.
Technical Risks: System impact, data consistency, performance degradation, integration complexity
Operational Risks: Service availability, deployment downtime, process changes, rollback procedures
Completion evidence: each evidenced material risk has likelihood/impact evidence and one preventive or containment control.
Transition: proceed when every high-impact risk has either a control or a blocking escalation.
Core Question: "What are this project's constraints?"
Check only constraints evidenced by the governing requirements, repository, external contracts, or current environment that can change the selected strategy or verification boundary.
Technical Constraints: Library compatibility, resource capacity, mandatory requirements, numerical targets
Temporal Constraints: Deadlines/priorities, dependencies, milestones, learning periods
Completion evidence: each constraint is observed, inferred, or unknown; every unknown that can invalidate a candidate names the exact evidence prerequisite.
Transition: proceed when remaining unknowns cannot change the valid candidate set, or the user resolves them.
Select the approach that satisfies all hard constraints and current requirements with the lowest transition risk and smallest verification delay. Use lifecycle cost and implementation effort only as tiebreakers after requirement coverage, compatibility, and risk control are equal.
Characteristics: Vertical implementation across all layers by feature unit Application Conditions: Low inter-feature dependencies, output in user-usable form, changes needed across all architecture layers Verification Method: End-user value delivery at each feature completion
Characteristics: Phased construction by architecture layer Application Conditions: Foundation system stability important, multiple features depend on common foundation, layer-by-layer verification effective Verification Method: Integrated operation verification when all foundation layers complete
Characteristics: Flexible combination according to project characteristics Application Conditions: Unclear requirements, need to change approach per phase, transition from prototyping to full implementation Verification Method: Assign L1 when the phase produces end-user-operable behavior, L2 when it produces a testable internal behavior or contract, and L3 only when the phase produces build-time structure with no runnable behavior yet
For Hybrid, assign one explicit L1/L2/L3 verification level and observable completion result to every phase.
Completion evidence: one selected approach, its phase boundaries, integration points, and a verification result for every phase.
Transition: proceed to documentation when the selected approach covers every hard constraint and its risks have controls. Otherwise return to candidate exploration (Phase 3), or to Design Convergence (Phase 2) when a Phase 4-5 result changes the Selected Design or its evidence.
Return the following structure in the Design Doc or planning handoff:
implementationApproachDecision:
observedConstraints: [<constraint + evidence>]
inferredConstraints: [<constraint + evidence and inference>]
unknowns: [<unknown + required evidence or decision>]
selectedApproach: <vertical | horizontal | hybrid description>
selectionRationale: <hard-constraint coverage, compatibility, risk control, and total-complexity basis>
addedDesignSurface: [<addition + current evidence + lower-surface insufficiency + subtraction result>]
phaseVerification: [<phase + L1/L2/L3 + observable completion evidence>]
Candidate approaches and rejection reasoning remain active analysis unless an accepted ADR owns them as decision history.
Completion evidence: the selected approach and every added design surface trace to an observed constraint, accepted inference, or resolved value-boundary decision.
Priority for completion verification of each task:
Priority: L1 > L2 > L3 in order of verifiability importance
Define integration points according to selected strategy:
When evidence required by a checked item is unknown, stop at that phase and report the exact repository evidence prerequisite. User interaction is required only when the unknown requires changing the outcome, desired-future requirements, or non-goals, or authorizing an irreversible action.
Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when planning feature implementation.
---name: implementation-approachdescription: Selects implementation strategy (vertical slice, horizontal, or hybrid) with risk assessment. Use when…---# .claude/skills-en/implementation-approach/SKILL.mdPerguntas frequentes
Baixe .claude/skills-en/implementation-approach/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/shinpr/ai-coding-project-boilerplate.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.