Menü
Helps create, analyze, and maintain Architecture Decision Records
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Generates comprehensive API documentation including OpenAPI/Swagger specs, endpoint descriptions, request/response examples, and integration guides. Use when documenting APIs.
Generate complete elizaOS character configurations with personality, knowledge, and plugin setup. Triggers when user asks to "create character", "generate agent config", or "build elizaOS character"
Execute the proper Drizzle Kit workflow for database schema migrations in asset-forge. Use this when the user asks to create a database migration, update the database schema, or when schema changes need to be applied to the database.
Integrates Lighthouse CI for automated performance testing, Core Web Vitals tracking, and regression detection in CI/CD pipelines. Use when user asks to "setup Lighthouse CI", "add performance testing", "monitor Core Web Vitals", or "prevent performance regressions".
Sets up visual regression testing using Percy, Chromatic, or Playwright to catch unintended UI changes through screenshot comparison. Use when user asks to "setup visual testing", "add screenshot tests", "prevent visual bugs", or "setup Percy/Chromatic".
Autonomously enforces TypeScript strict typing standards (ADR-0006)
| name | ADR Assistant |
| description | Helps create, analyze, and maintain Architecture Decision Records |
| trigger | Creating architectural decisions, evaluating alternatives, documenting technical choices |
I autonomously help with Architecture Decision Records when you're making architectural or technical decisions.
I trigger when you're:
${WORKSPACE_DIR}/adr/# NNNN. Title
Date: YYYY-MM-DD
## Status
Proposed | Accepted | Deprecated | Superseded
## Context
- Current situation
- Pain points
- Requirements
- Drivers
## Decision
What we decided and why
## Alternatives Considered
- Alt 1: Pros/Cons/Reason for rejection
- Alt 2: ...
## Consequences
- Positive
- Negative
- Neutral
- Risks with mitigations
## Implementation
- Action items
- Timeline
- Success metrics
## References
- Links to docs, commits, related ADRs
## Notes
- Additional insights
Next number: 0012
User: "Should we use GraphQL or REST for our new API?"
Me: I notice you're evaluating API architecture. Let me help create ADR-0012.
I'll:
adr/0012-api-architecture-choice.md