Extending to Tech Stacks

The core templates (AGENTS.md, CLAUDE.md, Jimmy’s Workflow) are technology-agnostic. They define workflow, principles, and project structure — not implementation choices.

For projects with specialised technology stacks, you can extend the system with domain-specific rule files that sit alongside AGENTS.md.

How it works

1. Set up core templates as normal
2. Create tech-specific rule files for your stack (e.g., aiken-development-rules.md, solidity-design-guide.md)
3. Reference them from AGENTS.md in the PROJECT_SPECIFIC_GUIDELINES section

<!-- In AGENTS.md -->
## Project-Specific Guidelines

See `aiken-development-rules.md` for Aiken smart contract patterns.
See `cardano-security-patterns.md` for EUTXO security considerations.

What tech-specific files contain

A good tech-specific rule file includes:

Section	Content
Language/framework patterns	Idioms, conventions, common structures
Security considerations	Domain-specific threats and mitigations
Testing patterns	How to test in this stack
Common pitfalls	What AI assistants get wrong in this domain
Tool configuration	IDE rules, linter config, build setup

The audit methodology also extends

The Audit MAP Methodology includes domain-specific severity uplift tables for:

• Children’s systems — COPPA compliance, parental consent
• Financial systems — Payment integrity, blockchain irrecoverability
• Cryptographic protocols — Nonce reuse, key material, timing attacks
• Health systems — GDPR special category, consent, biometric data

These demonstrate how the audit framework adapts to different risk domains.

Example domains

The template system has been used in production with:

• Blockchain smart contracts (Aiken/Plutus V3, Solidity)
• Cryptographic protocols (Noise XX, ML-KEM)
• Health/fitness applications
• Children’s education platforms
• Desktop applications (Tauri v2 + SolidJS)
• Rust backend services