Coding
Claude Artifacts Spec to Code Feature Pack
Claude Artifacts Spec to Code Feature Pack turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
The prompt
Claude Artifacts Spec to Code Feature Pack guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
text prompt
You are a senior engineer working in an existing codebase.
Feature name
{{featureName}}
Feature spec
{{featureSpec}}
Repo context
- Existing architecture overview: {{architectureOverview}}
- Key files or snippets (paste only what matters): {{keyCodeContext}}
- Constraints and conventions: {{repoConventions}}
Acceptance criteria
{{acceptanceCriteria}}
Hard requirements
1) Output as ONE Claude Artifact titled: "Feature Pack: {{featureName}}"
2) Work in this order:
a) Identify assumptions and missing info (max 8 questions). If you can proceed, write "None".
b) Implementation plan with step ordering and risk notes.
c) Code changes as unified diffs per file.
d) Tests (new or updated) with commands to run.
e) Documentation updates (README, API docs, or changelog if relevant).
Patch format (required)
For each changed file, output:
File: path/to/file.ext
```diff
unified diff here
```
Rules
- Keep changes minimal and consistent with existing patterns.
- Do not invent endpoints or DB tables unless the spec requires them.
- If you add dependencies, justify them and include install steps.
- Include a rollback plan if the change is risky.
Deliverable checklist
- All acceptance criteria are addressed explicitly
- Tests cover core logic and at least one edge case
- Errors have user-safe messages and logs have useful context
Tune the prompt, not the plumbing.
Every control comes from this prompt’s content schema. Changes stay in your browser and update instantly.
Customized prompt1420 characters
You are a senior engineer working in an existing codebase.
Feature name
a specific feature name
Feature spec
a specific feature spec
Repo context
- Existing architecture overview: a specific architecture overview
- Key files or snippets (paste only what matters): Paste the relevant source material and context here.
- Constraints and conventions: a specific repo conventions
Acceptance criteria
a specific acceptance criteria
Hard requirements
1) Output as ONE Claude Artifact titled: "Feature Pack: a specific feature name"
2) Work in this order:
a) Identify assumptions and missing info (max 8 questions). If you can proceed, write "None".
b) Implementation plan with step ordering and risk notes.
c) Code changes as unified diffs per file.
d) Tests (new or updated) with commands to run.
e) Documentation updates (README, API docs, or changelog if relevant).
Patch format (required)
For each changed file, output:
File: path/to/file.ext
```diff
unified diff here
```
Rules
- Keep changes minimal and consistent with existing patterns.
- Do not invent endpoints or DB tables unless the spec requires them.
- If you add dependencies, justify them and include install steps.
- Include a rollback plan if the change is risky.
Deliverable checklist
- All acceptance criteria are addressed explicitly
- Tests cover core logic and at least one edge case
- Errors have user-safe messages and logs have useful context
Useful structure, room to move.
Claude Artifacts Spec to Code Feature Pack guides the model through a defined task while preserving the source prompt's useful structure and constraints. Use it when planning, writing, reviewing, or debugging software and you want a response that is easier to evaluate and act on.
The prompt establishes the job first, then supplies concrete decisions a model can act on. The variables preserve that structure while letting you change the subject, context, or output.
Related prompts
Python Class Generator
Python Class Generator turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
API Endpoint Specification
API Endpoint Specification turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
Documentation Sweep for Onboarding
Documentation Sweep for Onboarding turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini
PR Description Review
PR Description Review turns technical context into clear code, diagnosis, or implementation guidance with clear constraints and an explicit output.
ChatGPTClaudeGemini