Menu
Generate AI-consumable coding rules (CLAUDE.md, .cursorrules, copilot-instructions) and enforcement tooling from SDL
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | coding-rules |
| description | Generate AI-consumable coding rules (CLAUDE.md, .cursorrules, copilot-instructions) and enforcement tooling from SDL |
Generate architecture-aware coding rules that AI coding tools (Claude Code, Cursor, GitHub Copilot) enforce automatically across every session. Optionally generates hard enforcement tooling (ESLint, dependency-cruiser, pre-commit hooks, architecture tests).
Input: SDL document
Output: CLAUDE.md, .cursorrules, .github/copilot-instructions.md, per-project CLAUDE.md, optional enforcement configs
A single markdown file (output to 3 locations for tool coverage) containing architecture-derived coding rules organized by category:
| Category | Source SDL Section | Example Rules |
|---|---|---|
| Architecture | architecture.style | Module boundary rules, service isolation, communication patterns |
| File Structure | architecture.projects | Framework conventions, ORM patterns, folder organization |
| Data Access | data | Repository pattern, database query rules, search engine usage |
| API Patterns | architecture.projects.backend | REST/GraphQL/gRPC conventions, versioning, service base paths |
| Authentication | auth | Provider-specific rules (Clerk/Auth0/Cognito), token handling, RBAC |
| Error Handling | errorHandling | Error format, global handler, circuit breaker, retry patterns |
| Integrations | integrations | Service client isolation, webhook handling, payment/email patterns |
| Testing | testing | Framework-specific rules, coverage targets, test structure |
| Observability | observability | Logging rules, tracing, metrics collection |
| Security | nonFunctional.security | PII handling, encryption, audit logging, OWASP compliance |
| Caching | data.cache | Cache invalidation, TTL, cache-aside pattern |
| Queues | data.queues | Message handling, idempotency, dead letter queues |
| Code Quality | (always generated) | SOLID principles, naming, DRY, single responsibility |
| Design Patterns | (always generated) | Framework-appropriate patterns (repository, factory, strategy) |
| File Size & Structure | (always generated) | Max file length, function complexity, extraction rules |
| API Design Quality | (always generated) | Pagination, filtering, consistent responses, HATEOAS |
| Database Queries | (always generated) | N+1 prevention, indexing, query optimization |
| Testing Quality | (always generated) | AAA pattern, test naming, mocking boundaries |
| Performance | (always generated) | Lazy loading, pagination, connection pooling |
| Import Organization | (always generated) | Import ordering, barrel exports, circular dependency prevention |
| Tech Debt Avoidance | (always generated) | TODO tracking, deprecation patterns, refactoring triggers |
| Resilience | (always generated) | Retry policies, timeouts, fallbacks, circuit breakers |
| Input Validation | (always generated) | Schema validation, sanitization, boundary validation |
| Concurrency | (always generated) | Race conditions, locking, atomic operations |
| Configuration | (always generated) | Env var patterns, secrets management, feature flags |
| Migration Safety | (always generated) | Backward compatibility, zero-downtime deploys, rollback |
| Documentation | (always generated) | When to document, inline comments, API docs |
| Git Workflow | (always generated) | Branch naming, commit messages, PR conventions |
| Category | Condition | Rules |
|---|---|---|
| Accessibility | Frontend projects exist | WCAG compliance, ARIA, keyboard navigation, color contrast |
| State Management | Frontend projects exist | Framework-specific state rules (React Context, Redux, Zustand) |
| Mobile | Mobile projects exist | Platform guidelines, navigation, permissions, offline |
| Internationalization | Multiple regions defined | i18n patterns, locale handling, RTL support |
For monorepo setups, generates {project-name}/CLAUDE.md with project-specific rules:
When coding-rules-enforcement is in artifacts.generate, produces hard gates:
| File | Purpose | Language |
|---|---|---|
.eslintrc.sdl.js | Custom ESLint rules from architecture | TypeScript/JS |
pyproject.sdl.toml | Ruff/flake8 config from architecture | Python |
.golangci.sdl.yml | golangci-lint config from architecture | Go |
.dependency-cruiser.sdl.cjs | Module boundary enforcement | TypeScript/JS |
.lintstagedrc.sdl.json | Pre-commit hook config | All |
tests/architecture.test.ts | Architecture conformance tests | TypeScript |
Rules are deterministic — same SDL input always produces identical output. The generator:
The generator tailors rules to the specific tech stack:
| Framework | Tailored Rules |
|---|---|
| Node.js/Express | Middleware patterns, async/await error handling, route organization |
| Python/FastAPI | Pydantic models, dependency injection, async endpoints |
| Go | Interface-based design, error wrapping, goroutine safety |
| .NET 8 | Controller patterns, DI container, middleware pipeline |
| Java/Spring | Bean lifecycle, AOP patterns, Spring Security |
| Next.js | App Router conventions, Server Components, RSC boundaries |
| React | Hook rules, component composition, render optimization |
/architect:scaffold — generate rules that match the scaffolded project structureCLAUDE.md into any project for instant architecture awarenesscoding-rules-enforcement artifact for CI/CD gatesThe coding rules generator is available as an SDL artifact type:
artifacts:
generate:
- coding-rules # Advisory rules (CLAUDE.md, .cursorrules, copilot-instructions)
- coding-rules-enforcement # Hard gates (ESLint, dependency-cruiser, pre-commit, arch tests)
Both are generated via the generate_from_sdl agent tool or the /api/sdl/generate endpoint.
Structured web research methodology for market analysis, competitor research, and technology evaluation. Ensures research uses live web data with source citations and confidence tags.
Mermaid diagram templates for solution architecture, service communication, C4 Context/Container, data flow, agent flow, deployment, and sequence diagrams. Use when generating architecture diagrams.
Solution Design Language (SDL) specification — schema, validation, normalization, and generation rules
Core methodology for analysing requirements, building system manifests, and generating architecture deliverables. Use when planning or designing any software architecture.
Extract and render all Mermaid diagrams from architecture blueprints to PNG images. Creates a diagrams/ folder with high-quality images ready for presentations and documentation.
Convert architecture documents (blueprints, stakeholder presentations) from Markdown to professionally formatted Word (.docx) files. Applies corporate styling, embeds PNG diagrams, and creates presentation-ready documents.