gabbe-kit 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +25 -0
- package/LICENSE-CODE +202 -0
- package/README.md +817 -0
- package/agents/AGENTS.md +542 -0
- package/agents/CONSTITUTION.md +188 -0
- package/agents/guides/00-index.md +142 -0
- package/agents/guides/ai/a2ui-protocols.md +71 -0
- package/agents/guides/ai/actor-agent-frameworks.md +82 -0
- package/agents/guides/ai/agent-communication.md +146 -0
- package/agents/guides/ai/agent-identity-trust.md +69 -0
- package/agents/guides/ai/agent-only-cognition.md +73 -0
- package/agents/guides/ai/agent-only-swarms.md +70 -0
- package/agents/guides/ai/agent-operating-ergonomics.md +52 -0
- package/agents/guides/ai/agent-ui.md +106 -0
- package/agents/guides/ai/ai-agentic.md +309 -0
- package/agents/guides/ai/beyond-llms.md +60 -0
- package/agents/guides/ai/dynamic-capability-loading.md +121 -0
- package/agents/guides/ai/gabbe-innovations.md +111 -0
- package/agents/guides/ai/model-customization-decisions.md +78 -0
- package/agents/guides/ai/multi-agent-systems.md +85 -0
- package/agents/guides/ai/self-evolving-skills.md +137 -0
- package/agents/guides/ai/self-healing-summary.md +21 -0
- package/agents/guides/ai/visual-mcp-integration.md +106 -0
- package/agents/guides/architecture/api-standards.md +61 -0
- package/agents/guides/architecture/blockchain-dlt.md +36 -0
- package/agents/guides/architecture/critical-systems-arch.md +66 -0
- package/agents/guides/architecture/event-driven-architecture.md +39 -0
- package/agents/guides/architecture/microservices.md +292 -0
- package/agents/guides/architecture/monolith.md +303 -0
- package/agents/guides/architecture/orchestration.md +75 -0
- package/agents/guides/architecture/system-qualities.md +51 -0
- package/agents/guides/architecture/system-scalability.md +47 -0
- package/agents/guides/architecture/systems-architecture.md +506 -0
- package/agents/guides/data/semantic-web.md +23 -0
- package/agents/guides/data/sql-nosql.md +305 -0
- package/agents/guides/industry/engineering-standards.md +36 -0
- package/agents/guides/industry/global-standards.md +24 -0
- package/agents/guides/industry/healthcare-fhir.md +33 -0
- package/agents/guides/industry/industrial-iot.md +33 -0
- package/agents/guides/industry/telecom-networks.md +34 -0
- package/agents/guides/languages/c-sharp.md +66 -0
- package/agents/guides/languages/go-lang.md +251 -0
- package/agents/guides/languages/java.md +73 -0
- package/agents/guides/languages/js-ts-nodejs.md +361 -0
- package/agents/guides/languages/nodejs-advanced.md +56 -0
- package/agents/guides/languages/php-laravel.md +376 -0
- package/agents/guides/languages/python-fastapi-ai.md +257 -0
- package/agents/guides/languages/rust.md +73 -0
- package/agents/guides/ops/compliance-audit.md +177 -0
- package/agents/guides/ops/cost-optimization.md +57 -0
- package/agents/guides/ops/dev-environments.md +67 -0
- package/agents/guides/ops/dev-workflow.md +44 -0
- package/agents/guides/ops/gabbe-cli-workflows.md +252 -0
- package/agents/guides/ops/production-health.md +62 -0
- package/agents/guides/ops/troubleshooting-guide.md +69 -0
- package/agents/guides/patterns/agentic-design-patterns.md +308 -0
- package/agents/guides/patterns/agentic-patterns.md +43 -0
- package/agents/guides/patterns/ai-native-scenarios.md +71 -0
- package/agents/guides/patterns/autonomous-swarm-patterns.md +42 -0
- package/agents/guides/patterns/design-patterns.md +68 -0
- package/agents/guides/patterns/enterprise-migration-scenario.md +58 -0
- package/agents/guides/patterns/enterprise-patterns.md +56 -0
- package/agents/guides/patterns/software-design-patterns.md +106 -0
- package/agents/guides/patterns/time-complexity-analysis.md +116 -0
- package/agents/guides/planning/product-requirements.md +407 -0
- package/agents/guides/planning/strategic-analysis.md +98 -0
- package/agents/guides/planning/visual-product-specs.md +162 -0
- package/agents/guides/principles/clean-code-standards.md +51 -0
- package/agents/guides/principles/computing-foundations.md +87 -0
- package/agents/guides/principles/diagramming-standards.md +568 -0
- package/agents/guides/principles/evaluation-strategy.md +103 -0
- package/agents/guides/principles/future-tech.md +35 -0
- package/agents/guides/principles/human-agent-collaboration.md +54 -0
- package/agents/guides/principles/legacy-tech.md +61 -0
- package/agents/guides/principles/mathematical-foundations.md +103 -0
- package/agents/guides/principles/modeling-methods.md +97 -0
- package/agents/guides/principles/no-code-integration.md +84 -0
- package/agents/guides/principles/testing-strategy.md +97 -0
- package/agents/guides/principles/visual-design-system.md +44 -0
- package/agents/guides/processes/RARV_CYCLE.md +262 -0
- package/agents/guides/processes/extension-protocol.md +183 -0
- package/agents/guides/processes/full-system-lifecycle.md +47 -0
- package/agents/guides/processes/knowledge-integration.md +82 -0
- package/agents/guides/processes/loki-sdlc-phases.md +446 -0
- package/agents/guides/product/green-software.md +38 -0
- package/agents/guides/product/sustainability-checks.md +29 -0
- package/agents/guides/security/ai-risk-standards-map.md +98 -0
- package/agents/guides/security/api-security.md +51 -0
- package/agents/guides/security/cryptography-standards.md +38 -0
- package/agents/guides/security/privacy-data-protection.md +41 -0
- package/agents/guides/security/secure-architecture.md +43 -0
- package/agents/guides/security/threat-modeling.md +46 -0
- package/agents/memory/AUDIT_LOG.md +48 -0
- package/agents/memory/CONTINUITY.md +49 -0
- package/agents/memory/PROJECT_STATE.md +134 -0
- package/agents/memory/RESUME_POINTER.md +15 -0
- package/agents/memory/episodic/DECISION_LOG_TEMPLATE.md +104 -0
- package/agents/memory/semantic/PROJECT_KNOWLEDGE_TEMPLATE.md +194 -0
- package/agents/memory/semantic/VECTOR_DB_CONFIG_TEMPLATE.json +46 -0
- package/agents/personas/00-index.md +148 -0
- package/agents/personas/biz-compliance.md +112 -0
- package/agents/personas/biz-legal.md +131 -0
- package/agents/personas/eng-api.md +110 -0
- package/agents/personas/eng-backend.md +113 -0
- package/agents/personas/eng-data.md +50 -0
- package/agents/personas/eng-database.md +95 -0
- package/agents/personas/eng-frontend.md +75 -0
- package/agents/personas/eng-infra.md +105 -0
- package/agents/personas/eng-messaging.md +50 -0
- package/agents/personas/eng-ml.md +50 -0
- package/agents/personas/eng-mobile.md +75 -0
- package/agents/personas/eng-perf.md +90 -0
- package/agents/personas/eng-qa.md +125 -0
- package/agents/personas/eng-tooling.md +49 -0
- package/agents/personas/ops-compliance.md +109 -0
- package/agents/personas/ops-cost.md +92 -0
- package/agents/personas/ops-devops.md +85 -0
- package/agents/personas/ops-incident.md +123 -0
- package/agents/personas/ops-monitor.md +89 -0
- package/agents/personas/ops-release.md +91 -0
- package/agents/personas/ops-security.md +104 -0
- package/agents/personas/ops-sre.md +85 -0
- package/agents/personas/orch-coordinator.md +140 -0
- package/agents/personas/orch-judge.md +135 -0
- package/agents/personas/orch-planner.md +114 -0
- package/agents/personas/orch-researcher.md +165 -0
- package/agents/personas/prod-architect.md +110 -0
- package/agents/personas/prod-design.md +112 -0
- package/agents/personas/prod-ethicist.md +50 -0
- package/agents/personas/prod-integration.md +120 -0
- package/agents/personas/prod-pm.md +115 -0
- package/agents/personas/prod-product-ops.md +128 -0
- package/agents/personas/prod-research.md +49 -0
- package/agents/personas/prod-safety-engineer.md +28 -0
- package/agents/personas/prod-tech-lead.md +119 -0
- package/agents/personas/ui-design.md +81 -0
- package/agents/scripts/check_skills_docs.py +120 -0
- package/agents/scripts/compile_skills.py +284 -0
- package/agents/scripts/comprehensive_checker.py +187 -0
- package/agents/scripts/dump-context.sh +37 -0
- package/agents/scripts/eval_skills.py +268 -0
- package/agents/scripts/preflight_summary.sh +80 -0
- package/agents/scripts/report_duplicates.py +125 -0
- package/agents/scripts/setup-context.ps1 +250 -0
- package/agents/scripts/setup-context.sh +398 -0
- package/agents/scripts/state_export.sh +84 -0
- package/agents/scripts/state_import.sh +99 -0
- package/agents/scripts/validate_integrity.py +98 -0
- package/agents/scripts/validate_links.py +96 -0
- package/agents/scripts/validate_methodology_graph.py +194 -0
- package/agents/scripts/validate_skills.py +81 -0
- package/agents/scripts/verify_e2e_init_flows.py +246 -0
- package/agents/scripts/verify_setup_simulation.py +104 -0
- package/agents/scripts/verify_triggers_and_mcps.py +159 -0
- package/agents/scripts/verify_use_cases.py +498 -0
- package/agents/skills/00-index.md +322 -0
- package/agents/skills/ai/a2ui-protocols.skill.md +31 -0
- package/agents/skills/ai/actor-agent-frameworks.skill.md +31 -0
- package/agents/skills/ai/agent-communication.skill.md +36 -0
- package/agents/skills/ai/agent-ui.skill.md +31 -0
- package/agents/skills/ai/autonomous-swarm-patterns.skill.md +31 -0
- package/agents/skills/ai/beyond-llms.skill.md +31 -0
- package/agents/skills/ai/context-engineering.skill.md +79 -0
- package/agents/skills/ai/llm-as-judge.skill.md +97 -0
- package/agents/skills/ai/multi-agent-systems.skill.md +31 -0
- package/agents/skills/ai/rag-evaluation.skill.md +93 -0
- package/agents/skills/ai/reasoning-patterns.skill.md +125 -0
- package/agents/skills/architecture/adaptive-architecture.skill.md +51 -0
- package/agents/skills/architecture/api-design.skill.md +92 -0
- package/agents/skills/architecture/api-standards.skill.md +31 -0
- package/agents/skills/architecture/arch-debt.skill.md +180 -0
- package/agents/skills/architecture/arch-design.skill.md +304 -0
- package/agents/skills/architecture/arch-patterns.skill.md +52 -0
- package/agents/skills/architecture/arch-review.skill.md +326 -0
- package/agents/skills/architecture/architecture-governance.skill.md +62 -0
- package/agents/skills/architecture/attribute-driven-design.skill.md +108 -0
- package/agents/skills/architecture/blockchain-dlt.skill.md +28 -0
- package/agents/skills/architecture/compatibility-design.skill.md +51 -0
- package/agents/skills/architecture/critical-systems-arch.skill.md +31 -0
- package/agents/skills/architecture/design-patterns.skill.md +59 -0
- package/agents/skills/architecture/diagramming.skill.md +380 -0
- package/agents/skills/architecture/domain-model.skill.md +294 -0
- package/agents/skills/architecture/enterprise-migration-scenario.skill.md +31 -0
- package/agents/skills/architecture/enterprise-patterns.skill.md +31 -0
- package/agents/skills/architecture/error-handling-strategy.skill.md +58 -0
- package/agents/skills/architecture/event-driven-architecture.skill.md +31 -0
- package/agents/skills/architecture/event-governance.skill.md +55 -0
- package/agents/skills/architecture/fitness-functions.skill.md +111 -0
- package/agents/skills/architecture/graphql-schema.skill.md +64 -0
- package/agents/skills/architecture/legacy-modernization.skill.md +51 -0
- package/agents/skills/architecture/microservices.skill.md +31 -0
- package/agents/skills/architecture/middleware-design.skill.md +59 -0
- package/agents/skills/architecture/monolith.skill.md +31 -0
- package/agents/skills/architecture/realtime-comm.skill.md +52 -0
- package/agents/skills/architecture/state-management.skill.md +72 -0
- package/agents/skills/architecture/system-qualities.skill.md +31 -0
- package/agents/skills/architecture/system-scalability.skill.md +31 -0
- package/agents/skills/architecture/systems-architecture.skill.md +31 -0
- package/agents/skills/architecture/visual-whiteboarding.skill.md +33 -0
- package/agents/skills/brain/README.md +70 -0
- package/agents/skills/brain/active-inference.skill.md +74 -0
- package/agents/skills/brain/brain-mode.skill.md +125 -0
- package/agents/skills/brain/cognitive-architectures.skill.md +53 -0
- package/agents/skills/brain/cognitive-testing.skill.md +62 -0
- package/agents/skills/brain/consciousness-loop.skill.md +68 -0
- package/agents/skills/brain/cost-benefit-router.skill.md +89 -0
- package/agents/skills/brain/episodic-consolidation.skill.md +43 -0
- package/agents/skills/brain/epistemology-knowledge.skill.md +54 -0
- package/agents/skills/brain/global-workspace.skill.md +77 -0
- package/agents/skills/brain/learning-adaptation.skill.md +68 -0
- package/agents/skills/brain/loki-mode.skill.md +267 -0
- package/agents/skills/brain/neuroscience-foundations.skill.md +52 -0
- package/agents/skills/brain/scripts/active_inference_loop.py +92 -0
- package/agents/skills/brain/scripts/cognition_test.py +80 -0
- package/agents/skills/brain/scripts/global_workspace.py +104 -0
- package/agents/skills/brain/self-improvement.skill.md +80 -0
- package/agents/skills/brain/sensory-motor.skill.md +61 -0
- package/agents/skills/brain/sequential-thinking.skill.md +48 -0
- package/agents/skills/brain/working-memory.skill.md +47 -0
- package/agents/skills/coding/agent-trajectory-eval.skill.md +92 -0
- package/agents/skills/coding/artisan-commands.skill.md +52 -0
- package/agents/skills/coding/browser-tdd.skill.md +131 -0
- package/agents/skills/coding/chaos-fault-injection.skill.md +116 -0
- package/agents/skills/coding/ci-autofix.skill.md +53 -0
- package/agents/skills/coding/clean-coder.skill.md +58 -0
- package/agents/skills/coding/code-review.skill.md +100 -0
- package/agents/skills/coding/debug.skill.md +100 -0
- package/agents/skills/coding/documentation.skill.md +149 -0
- package/agents/skills/coding/eval-driven-development.skill.md +107 -0
- package/agents/skills/coding/evals/code-review.eval.yaml +29 -0
- package/agents/skills/coding/excalidraw.skill.md +90 -0
- package/agents/skills/coding/file-processing.skill.md +55 -0
- package/agents/skills/coding/git-workflow.skill.md +153 -0
- package/agents/skills/coding/metamorphic-testing.skill.md +113 -0
- package/agents/skills/coding/mobile-dev.skill.md +41 -0
- package/agents/skills/coding/nodejs-expert.skill.md +23 -0
- package/agents/skills/coding/output-validation.skill.md +57 -0
- package/agents/skills/coding/pbt-strategy.skill.md +117 -0
- package/agents/skills/coding/performant-ai.skill.md +62 -0
- package/agents/skills/coding/performant-go.skill.md +61 -0
- package/agents/skills/coding/performant-laravel.skill.md +70 -0
- package/agents/skills/coding/performant-nodejs.skill.md +67 -0
- package/agents/skills/coding/performant-php.skill.md +53 -0
- package/agents/skills/coding/performant-python.skill.md +62 -0
- package/agents/skills/coding/refactor.skill.md +124 -0
- package/agents/skills/coding/secure-coding.skill.md +57 -0
- package/agents/skills/coding/sketch-to-diagram.skill.md +106 -0
- package/agents/skills/coding/spec-driven-development.skill.md +110 -0
- package/agents/skills/coding/tdd-cycle.skill.md +92 -0
- package/agents/skills/coding/testing-strategy.skill.md +74 -0
- package/agents/skills/coding/time-complexity.skill.md +112 -0
- package/agents/skills/coding/tldraw-canvas.skill.md +109 -0
- package/agents/skills/coding/tool-construction.skill.md +47 -0
- package/agents/skills/coding/ui-gen.skill.md +64 -0
- package/agents/skills/coding/vibe-coding.skill.md +63 -0
- package/agents/skills/coding/visual-design.skill.md +65 -0
- package/agents/skills/coordination/agent-interop.skill.md +72 -0
- package/agents/skills/coordination/agent-protocol.skill.md +62 -0
- package/agents/skills/coordination/agent-workflow-patterns.skill.md +123 -0
- package/agents/skills/coordination/agentic-linter.skill.md +134 -0
- package/agents/skills/coordination/agentic-patterns.skill.md +79 -0
- package/agents/skills/coordination/meta-optimize.skill.md +62 -0
- package/agents/skills/coordination/meta-prompting.skill.md +46 -0
- package/agents/skills/coordination/multi-agent-orch.skill.md +78 -0
- package/agents/skills/coordination/persona-selector.skill.md +78 -0
- package/agents/skills/coordination/self-optimize.skill.md +81 -0
- package/agents/skills/coordination/swarm-consensus.skill.md +52 -0
- package/agents/skills/core/agent-analytics.skill.md +74 -0
- package/agents/skills/core/audit-trail.skill.md +122 -0
- package/agents/skills/core/clarify.skill.md +89 -0
- package/agents/skills/core/emerging-tech.skill.md +52 -0
- package/agents/skills/core/empirical-methods.skill.md +101 -0
- package/agents/skills/core/evals/clarify.eval.yaml +29 -0
- package/agents/skills/core/evals/integrity-check.eval.yaml +23 -0
- package/agents/skills/core/evals/research.eval.yaml +23 -0
- package/agents/skills/core/final-review.skill.md +66 -0
- package/agents/skills/core/integrity-check.skill.md +149 -0
- package/agents/skills/core/knowledge-connect.skill.md +77 -0
- package/agents/skills/core/knowledge-gap.skill.md +123 -0
- package/agents/skills/core/preflight.skill.md +106 -0
- package/agents/skills/core/research.skill.md +107 -0
- package/agents/skills/core/retrospective.skill.md +59 -0
- package/agents/skills/core/sdlc-checkpoint.skill.md +151 -0
- package/agents/skills/core/self-heal.skill.md +163 -0
- package/agents/skills/core/session-resume.skill.md +125 -0
- package/agents/skills/core/skills-registry.skill.md +65 -0
- package/agents/skills/core/state-portability.skill.md +89 -0
- package/agents/skills/core/state-preserve.skill.md +76 -0
- package/agents/skills/core/system-lifecycle.skill.md +51 -0
- package/agents/skills/core/update-scan.skill.md +92 -0
- package/agents/skills/data/data-engineering.skill.md +56 -0
- package/agents/skills/data/data-governance.skill.md +49 -0
- package/agents/skills/data/db-migration.skill.md +136 -0
- package/agents/skills/data/semantic-web.skill.md +28 -0
- package/agents/skills/data/sql-optimization.skill.md +78 -0
- package/agents/skills/industry/engineering-standards.skill.md +31 -0
- package/agents/skills/industry/global-standards.skill.md +30 -0
- package/agents/skills/industry/healthcare-fhir.skill.md +28 -0
- package/agents/skills/industry/industrial-iot.skill.md +30 -0
- package/agents/skills/industry/telecom-networks.skill.md +30 -0
- package/agents/skills/ops/caching-strategy.skill.md +77 -0
- package/agents/skills/ops/capacity-planning.skill.md +67 -0
- package/agents/skills/ops/cloud-deploy.skill.md +55 -0
- package/agents/skills/ops/configuration-management.skill.md +107 -0
- package/agents/skills/ops/cost-optimization.skill.md +39 -0
- package/agents/skills/ops/decommission-sunset.skill.md +64 -0
- package/agents/skills/ops/dependency-lifecycle.skill.md +63 -0
- package/agents/skills/ops/deployment.skill.md +217 -0
- package/agents/skills/ops/dev-environments.skill.md +31 -0
- package/agents/skills/ops/dev-workflow.skill.md +28 -0
- package/agents/skills/ops/docker-dev.skill.md +52 -0
- package/agents/skills/ops/enterprise-integration.skill.md +53 -0
- package/agents/skills/ops/feature-flag-management.skill.md +59 -0
- package/agents/skills/ops/incident-response.skill.md +40 -0
- package/agents/skills/ops/infra-devops.skill.md +53 -0
- package/agents/skills/ops/k8s-dev.skill.md +51 -0
- package/agents/skills/ops/memory-optimization.skill.md +45 -0
- package/agents/skills/ops/observability-stack-setup.skill.md +62 -0
- package/agents/skills/ops/performance-audit.skill.md +178 -0
- package/agents/skills/ops/performance-optimization.skill.md +51 -0
- package/agents/skills/ops/production-health.skill.md +85 -0
- package/agents/skills/ops/production-verifier.skill.md +50 -0
- package/agents/skills/ops/queue-management.skill.md +52 -0
- package/agents/skills/ops/release-management.skill.md +39 -0
- package/agents/skills/ops/release-validation.skill.md +51 -0
- package/agents/skills/ops/reliability-sre.skill.md +51 -0
- package/agents/skills/ops/runbook-authoring.skill.md +64 -0
- package/agents/skills/ops/system-benchmark.skill.md +69 -0
- package/agents/skills/ops/tech-debt.skill.md +143 -0
- package/agents/skills/ops/troubleshooting-guide.skill.md +31 -0
- package/agents/skills/product/accessibility.skill.md +143 -0
- package/agents/skills/product/adr-writer.skill.md +110 -0
- package/agents/skills/product/business-case.skill.md +70 -0
- package/agents/skills/product/change-management.skill.md +90 -0
- package/agents/skills/product/decompose.skill.md +75 -0
- package/agents/skills/product/design-thinking.skill.md +62 -0
- package/agents/skills/product/estimation-sizing.skill.md +87 -0
- package/agents/skills/product/evals/spec-writer.eval.yaml +22 -0
- package/agents/skills/product/financial-governance.skill.md +88 -0
- package/agents/skills/product/green-software.skill.md +46 -0
- package/agents/skills/product/ideation-facilitation.skill.md +87 -0
- package/agents/skills/product/market-analysis.skill.md +56 -0
- package/agents/skills/product/opportunity-assessment.skill.md +89 -0
- package/agents/skills/product/product-analytics.skill.md +92 -0
- package/agents/skills/product/professional-practice.skill.md +105 -0
- package/agents/skills/product/req-elicitation.skill.md +292 -0
- package/agents/skills/product/req-review.skill.md +280 -0
- package/agents/skills/product/spec-analyze.skill.md +98 -0
- package/agents/skills/product/spec-writer.skill.md +114 -0
- package/agents/skills/product/stakeholder-management.skill.md +54 -0
- package/agents/skills/product/sustainability-checks.skill.md +29 -0
- package/agents/skills/product/systems-thinking.skill.md +56 -0
- package/agents/skills/product/user-research-synthesis.skill.md +85 -0
- package/agents/skills/product/user-story-mapping.skill.md +54 -0
- package/agents/skills/product/visual-specs.skill.md +112 -0
- package/agents/skills/security/access-control.skill.md +45 -0
- package/agents/skills/security/agent-sandboxing.skill.md +69 -0
- package/agents/skills/security/ai-ethics-compliance.skill.md +46 -0
- package/agents/skills/security/ai-red-teaming.skill.md +74 -0
- package/agents/skills/security/ai-safety-guardrails.skill.md +60 -0
- package/agents/skills/security/api-security.skill.md +31 -0
- package/agents/skills/security/backup-recovery.skill.md +49 -0
- package/agents/skills/security/compliance-review.skill.md +152 -0
- package/agents/skills/security/cryptography-standards.skill.md +31 -0
- package/agents/skills/security/dependency-security.skill.md +47 -0
- package/agents/skills/security/hazard-analysis.skill.md +53 -0
- package/agents/skills/security/legal-review.skill.md +41 -0
- package/agents/skills/security/log-analysis.skill.md +68 -0
- package/agents/skills/security/network-security.skill.md +64 -0
- package/agents/skills/security/privacy-audit.skill.md +137 -0
- package/agents/skills/security/privacy-data-protection.skill.md +31 -0
- package/agents/skills/security/prompt-injection-defense.skill.md +67 -0
- package/agents/skills/security/reliability-engineering.skill.md +47 -0
- package/agents/skills/security/safety-scan.skill.md +49 -0
- package/agents/skills/security/secrets-management.skill.md +65 -0
- package/agents/skills/security/secure-architecture.skill.md +31 -0
- package/agents/skills/security/security-audit.skill.md +164 -0
- package/agents/skills/security/threat-model.skill.md +120 -0
- package/agents/skills/security/traceability-audit.skill.md +48 -0
- package/agents/templates/00-index.md +162 -0
- package/agents/templates/architecture/ADAPTIVE_SYSTEM_TEMPLATE.md +35 -0
- package/agents/templates/architecture/ADD_WORKBOOK_TEMPLATE.md +81 -0
- package/agents/templates/architecture/ADR_TEMPLATE.md +136 -0
- package/agents/templates/architecture/ARCHITECTURE_DECISION_MATRIX.md +169 -0
- package/agents/templates/architecture/ARCHITECTURE_REVIEW_TEMPLATE.md +241 -0
- package/agents/templates/architecture/ARCHITECTURE_VIEWS_TEMPLATE.md +353 -0
- package/agents/templates/architecture/ARCH_DECISION_FRAMEWORK.md +32 -0
- package/agents/templates/architecture/C4_ARCHITECTURE_TEMPLATE.md +185 -0
- package/agents/templates/architecture/CAPABILITY_MAP_TEMPLATE.md +153 -0
- package/agents/templates/architecture/CONTEXT_MAP_TEMPLATE.md +196 -0
- package/agents/templates/architecture/DESIGN_PATTERN_USAGE.md +24 -0
- package/agents/templates/architecture/DOMAIN_MODEL_TEMPLATE.md +254 -0
- package/agents/templates/architecture/FITNESS_FUNCTION_TEMPLATE.md +59 -0
- package/agents/templates/architecture/INTEGRATION_SPEC_TEMPLATE.md +38 -0
- package/agents/templates/architecture/LEGACY_AUDIT_TEMPLATE.md +34 -0
- package/agents/templates/architecture/QUALITY_ATTRIBUTES_TEMPLATE.md +210 -0
- package/agents/templates/architecture/SCALABILITY_ANALYSIS_TEMPLATE.md +46 -0
- package/agents/templates/architecture/SMART_CONTRACT_TEMPLATE.md +44 -0
- package/agents/templates/architecture/SYSTEM_CONTEXT_TEMPLATE.md +197 -0
- package/agents/templates/brain/ACTIVE_INFERENCE_LOOP_TEMPLATE.md +42 -0
- package/agents/templates/brain/EPISODIC_MEMORY_LOG_TEMPLATE.md +28 -0
- package/agents/templates/brain/GLOBAL_WORKSPACE_CONFIG_TEMPLATE.md +44 -0
- package/agents/templates/brain/KNOWLEDGE_MAP_TEMPLATE.md +53 -0
- package/agents/templates/brain/OODA_LOOP_TRACE_TEMPLATE.md +44 -0
- package/agents/templates/brain/PREDICTION_ERROR_LOG_TEMPLATE.md +33 -0
- package/agents/templates/brain/PROJECT_CONTEXT_TEMPLATE.md +36 -0
- package/agents/templates/brain/SELF_IMPROVEMENT_LOG_TEMPLATE.md +39 -0
- package/agents/templates/brain/WORKING_MEMORY_TEMPLATE.md +34 -0
- package/agents/templates/coding/CLEAN_CODE_CHECKLIST.md +30 -0
- package/agents/templates/coding/DESIGN_TOKENS_TEMPLATE.json +54 -0
- package/agents/templates/coding/DEVCONTAINER_TEMPLATE.json +42 -0
- package/agents/templates/coding/DEV_SPACE_TEMPLATE.yaml +48 -0
- package/agents/templates/coding/E2E_TEST_SUITE_TEMPLATE.md +36 -0
- package/agents/templates/coding/EVAL_PLAN_TEMPLATE.md +85 -0
- package/agents/templates/coding/EVAL_RUBRIC_TEMPLATE.md +57 -0
- package/agents/templates/coding/GOLDEN_DATASET_TEMPLATE.md +73 -0
- package/agents/templates/coding/PROPERTY_TEST_CHECKLIST.md +77 -0
- package/agents/templates/coding/SKETCH_TO_DIAGRAM_TEMPLATE.md +56 -0
- package/agents/templates/coding/TEST_CASE_TEMPLATE.md +28 -0
- package/agents/templates/coding/TEST_PLAN_TEMPLATE.md +36 -0
- package/agents/templates/coding/TIME_COMPLEXITY_REPORT_TEMPLATE.md +61 -0
- package/agents/templates/coordination/AGENTS_TEMPLATE.md +540 -0
- package/agents/templates/coordination/AGENT_HANDSHAKE_TEMPLATE.json +37 -0
- package/agents/templates/coordination/AGENT_PROFILE_TEMPLATE.md +28 -0
- package/agents/templates/coordination/SWARM_ARCHITECTURE_TEMPLATE.md +53 -0
- package/agents/templates/coordination/SWARM_CONFIG_TEMPLATE.json +45 -0
- package/agents/templates/core/AUDIT_LOG_TEMPLATE.md +75 -0
- package/agents/templates/core/BUG_REPORT_TEMPLATE.md +136 -0
- package/agents/templates/core/DEPENDENCY_GRAPH_TEMPLATE.md +63 -0
- package/agents/templates/core/ESTIMATION_TEMPLATE.md +70 -0
- package/agents/templates/core/MCP_CONFIG_TEMPLATE.json +807 -0
- package/agents/templates/core/PLAN_TEMPLATE.md +162 -0
- package/agents/templates/core/PROJECT_RETROSPECTIVE_TEMPLATE.md +67 -0
- package/agents/templates/core/SDLC_TRACKER.md +217 -0
- package/agents/templates/core/SESSION_SNAPSHOT_TEMPLATE.md +168 -0
- package/agents/templates/core/SYSTEM_ANALYSIS_TEMPLATE.md +52 -0
- package/agents/templates/core/TASKS_TEMPLATE.md +104 -0
- package/agents/templates/core/TRACEABILITY_MATRIX_TEMPLATE.md +18 -0
- package/agents/templates/core/WHITEBOARD_DESIGN_TEMPLATE.md +46 -0
- package/agents/templates/data/DATABASE_SCHEMA_TEMPLATE.md +38 -0
- package/agents/templates/data/DATA_PIPELINE_TEMPLATE.md +44 -0
- package/agents/templates/data/ONTOLOGY_TEMPLATE.md +52 -0
- package/agents/templates/industry/ENGINEERING_STANDARDS_REVIEW_TEMPLATE.md +43 -0
- package/agents/templates/industry/FHIR_INTEGRATION_TEMPLATE.md +53 -0
- package/agents/templates/industry/GLOBAL_STANDARDS_AUDIT_TEMPLATE.md +45 -0
- package/agents/templates/industry/IOT_TELEMETRY_TEMPLATE.md +59 -0
- package/agents/templates/industry/TELECOM_API_TEMPLATE.md +50 -0
- package/agents/templates/ops/BENCHMARK_REPORT_TEMPLATE.md +48 -0
- package/agents/templates/ops/CAPACITY_PLAN_TEMPLATE.md +41 -0
- package/agents/templates/ops/COST_OPTIMIZATION_REPORT_TEMPLATE.md +40 -0
- package/agents/templates/ops/DECOMMISSION_PLAN_TEMPLATE.md +102 -0
- package/agents/templates/ops/DEPLOY_CONFIG_TEMPLATE.md +88 -0
- package/agents/templates/ops/INCIDENT_POSTMORTEM_TEMPLATE.md +39 -0
- package/agents/templates/ops/INFRA_PLAN_TEMPLATE.md +37 -0
- package/agents/templates/ops/RELEASE_READINESS_REPORT.md +35 -0
- package/agents/templates/ops/RUNBOOK_TEMPLATE.md +103 -0
- package/agents/templates/ops/TECH_DEBT_TEMPLATE.md +102 -0
- package/agents/templates/product/BUSINESS_CASE_TEMPLATE.md +42 -0
- package/agents/templates/product/CHANGE_MANAGEMENT_PLAN_TEMPLATE.md +68 -0
- package/agents/templates/product/EMPATHY_MAP_TEMPLATE.md +47 -0
- package/agents/templates/product/EXPERIMENT_PLAN_TEMPLATE.md +84 -0
- package/agents/templates/product/GREEN_SOFTWARE_REPORT_TEMPLATE.md +42 -0
- package/agents/templates/product/IDEATION_LOG_TEMPLATE.md +42 -0
- package/agents/templates/product/NFR_TEMPLATE.md +31 -0
- package/agents/templates/product/PRD_TEMPLATE.md +222 -0
- package/agents/templates/product/PROBLEM_STATEMENT_TEMPLATE.md +32 -0
- package/agents/templates/product/REQUIREMENTS_REVIEW_TEMPLATE.md +173 -0
- package/agents/templates/product/SPEC_TEMPLATE.md +259 -0
- package/agents/templates/product/STAKEHOLDER_REGISTER_TEMPLATE.md +127 -0
- package/agents/templates/product/USER_STORY_MAP_TEMPLATE.md +35 -0
- package/agents/templates/product/VISUAL_SPEC_PACKAGE_TEMPLATE.md +207 -0
- package/agents/templates/security/DATASHEET_TEMPLATE.md +95 -0
- package/agents/templates/security/ETHICAL_IMPACT_ASSESSMENT.md +32 -0
- package/agents/templates/security/HAZARD_LOG.md +17 -0
- package/agents/templates/security/MODEL_CARD_TEMPLATE.md +120 -0
- package/agents/templates/security/SAFETY_CASE.md +39 -0
- package/agents/templates/security/SAFETY_POLICY.md +25 -0
- package/agents/templates/security/SECURITY_CHECKLIST.md +157 -0
- package/agents/templates/security/SYSTEM_CARD_TEMPLATE.md +139 -0
- package/agents/templates/security/THREAT_MODEL_TEMPLATE.md +171 -0
- package/bin/install.js +572 -0
- package/docs/CLI_REFERENCE.md +527 -0
- package/docs/INSTALL.md +68 -0
- package/docs/MCP_CONFIGURATIONS.md +1765 -0
- package/docs/PLATFORM_CONTROLS.md +324 -0
- package/docs/POST_INSTALL.md +75 -0
- package/docs/QUICK_COMMANDS.md +131 -0
- package/docs/QUICK_GUIDE.md +914 -0
- package/docs/README_FULL.md +1451 -0
- package/docs/SCHEMA.md +164 -0
- package/docs/V1_RELEASE_CHECKLIST.md +144 -0
- package/docs/VERIFICATION_GUIDE.md +283 -0
- package/docs/adr/0001-record-architecture-decisions.md +26 -0
- package/docs/adr/0002-brain-active-inference-runtime.md +27 -0
- package/docs/adr/0003-additive-only-emitter-schema-evolution.md +33 -0
- package/docs/assets/GABBE.png +0 -0
- package/docs/gabbe.config.example.json +9 -0
- package/docs/reports/duplication-report.md +30 -0
- package/install.ps1 +90 -0
- package/install.sh +89 -0
- package/package.json +49 -0
- package/scripts/init.py +1036 -0
|
@@ -0,0 +1,326 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: arch-review
|
|
3
|
+
description: Review existing architecture (ATAM-lite) against quality-attribute scenarios; find risks, tradeoffs, anti-patterns; report.
|
|
4
|
+
triggers: [review architecture, audit architecture, architecture analysis, architecture assessment, arch review, evaluate architecture, is the architecture good, architecture problems, existing architecture]
|
|
5
|
+
tags: [architecture]
|
|
6
|
+
core: true
|
|
7
|
+
context_cost: high
|
|
8
|
+
---
|
|
9
|
+
# Architecture Review Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
|
|
13
|
+
Evaluate an existing architecture for fitness against its stated requirements,
|
|
14
|
+
identify risks and anti-patterns, and produce a structured review report with
|
|
15
|
+
concrete recommendations. Based on ATAM (Architecture Tradeoff Analysis Method)
|
|
16
|
+
adapted for single-agent use.
|
|
17
|
+
|
|
18
|
+
---
|
|
19
|
+
|
|
20
|
+
## When to Use
|
|
21
|
+
|
|
22
|
+
- **Scenario 2 (Review existing)**: Architecture exists — documented or inferred from code.
|
|
23
|
+
- Before major changes: "Is this architecture adequate for the new requirements?"
|
|
24
|
+
- After significant growth: "Is this architecture still appropriate?"
|
|
25
|
+
- Before technology migration: "What architectural problems must we solve?"
|
|
26
|
+
- Due diligence: "Is this architecture sound before we commit to it?"
|
|
27
|
+
|
|
28
|
+
---
|
|
29
|
+
|
|
30
|
+
## Step 1 — Understand the Architecture Inputs
|
|
31
|
+
|
|
32
|
+
```
|
|
33
|
+
Gather before starting the review:
|
|
34
|
+
|
|
35
|
+
Architectural artifacts (work with whatever exists):
|
|
36
|
+
□ Architecture document, README, or description
|
|
37
|
+
□ Diagrams (any level — C4, UML, whiteboard photo, etc.)
|
|
38
|
+
□ Requirements, PRD, or feature descriptions
|
|
39
|
+
□ Codebase structure (actual source of truth if docs are outdated)
|
|
40
|
+
□ Deployment configuration (shows actual runtime structure)
|
|
41
|
+
□ ADRs or documented decisions
|
|
42
|
+
|
|
43
|
+
If artifacts are sparse or missing:
|
|
44
|
+
→ Reverse-engineer the architecture from the codebase
|
|
45
|
+
→ Use tools: dependency graphs, import analysis, directory structure
|
|
46
|
+
→ Document what you find — the architecture review creates the documentation
|
|
47
|
+
|
|
48
|
+
Key questions to answer in this step:
|
|
49
|
+
1. What business/user goals does this system serve?
|
|
50
|
+
2. What is the system's domain and boundaries?
|
|
51
|
+
3. What are the stated or implied quality requirements?
|
|
52
|
+
4. What architectural style appears to be in use?
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
## Step 2 — Reconstruct Architecture Description
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
If no architecture documentation exists, create a description from code/config:
|
|
61
|
+
|
|
62
|
+
System Context:
|
|
63
|
+
- What are the external actors (users, systems)?
|
|
64
|
+
- What are the major integration points?
|
|
65
|
+
Create: System Context diagram (C4 Level 1)
|
|
66
|
+
|
|
67
|
+
Component Inventory:
|
|
68
|
+
- What are the major components/services/modules?
|
|
69
|
+
- What does each one do?
|
|
70
|
+
- How do they communicate?
|
|
71
|
+
Create: Container/Component diagram
|
|
72
|
+
|
|
73
|
+
Data Flows:
|
|
74
|
+
- Where does data enter the system?
|
|
75
|
+
- How does it flow between components?
|
|
76
|
+
- Where is it stored?
|
|
77
|
+
|
|
78
|
+
Interface Inventory:
|
|
79
|
+
- What interfaces exist between components?
|
|
80
|
+
- What protocols are used?
|
|
81
|
+
- What contracts are enforced?
|
|
82
|
+
|
|
83
|
+
Fill: templates/architecture/ARCHITECTURE_VIEWS_TEMPLATE.md with the reconstructed architecture.
|
|
84
|
+
This becomes the baseline for the review.
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## Step 3 — Quality Attribute Scenario Analysis (ATAM core)
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
Identify or derive Quality Attribute Scenarios (QAS):
|
|
93
|
+
Source: PRD, SPEC, stakeholder interviews, SLOs, implicit system behavior
|
|
94
|
+
|
|
95
|
+
For each QAS, evaluate: does the architecture satisfy it?
|
|
96
|
+
|
|
97
|
+
Evaluation framework:
|
|
98
|
+
SATISFIED: Architecture demonstrably meets this QAS
|
|
99
|
+
PARTIALLY: Architecture meets it under some conditions but not all
|
|
100
|
+
AT RISK: Architecture may not meet this under stress/failure conditions
|
|
101
|
+
VIOLATED: Architecture structurally cannot meet this QAS
|
|
102
|
+
|
|
103
|
+
Example QAS evaluation:
|
|
104
|
+
QAS: "WHEN 10,000 concurrent users access the search feature,
|
|
105
|
+
the system SHALL return results in < 2 seconds."
|
|
106
|
+
Evaluation: AT RISK — current architecture uses synchronous database queries
|
|
107
|
+
without caching. Under 10k users this will likely exceed 2s.
|
|
108
|
+
Evidence: [describe the structural reason]
|
|
109
|
+
Mitigation: [what architectural change would address this]
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## Step 4 — Identify Architecture Smells
|
|
115
|
+
|
|
116
|
+
```
|
|
117
|
+
Check for common architecture anti-patterns:
|
|
118
|
+
|
|
119
|
+
Structural smells:
|
|
120
|
+
□ God Component: one component with too many responsibilities
|
|
121
|
+
Signs: > 30% of all code in one module, imports from everywhere
|
|
122
|
+
□ Inappropriate Intimacy: components know too much about each other's internals
|
|
123
|
+
Signs: direct access to internal data structures, bypass of interfaces
|
|
124
|
+
□ Cyclic Dependencies: Component A → B → C → A
|
|
125
|
+
Signs: circular import graphs, cannot test one without the other
|
|
126
|
+
□ Bottleneck Component: single component that all others depend on
|
|
127
|
+
Signs: high afferent coupling (many components depend on this one)
|
|
128
|
+
□ Scattered Functionality: one feature spread across many unrelated components
|
|
129
|
+
Signs: a single user action triggers changes in 10+ components
|
|
130
|
+
□ Hidden Coupling: components appear independent but share implicit state
|
|
131
|
+
Signs: shared mutable global state, shared database tables with mixed access
|
|
132
|
+
|
|
133
|
+
Layering smells:
|
|
134
|
+
□ Layer Skipping: presentation layer directly accessing data layer
|
|
135
|
+
□ Layer Inversion: inner layer (domain) importing outer layer (infrastructure)
|
|
136
|
+
□ Fat Layer: all logic in one layer (fat controller, fat database)
|
|
137
|
+
|
|
138
|
+
Deployment smells:
|
|
139
|
+
□ Deployment Monolith: one deployment unit but logically many services
|
|
140
|
+
□ Chatty Services: services making many fine-grained calls to each other
|
|
141
|
+
□ Data Coupling: services sharing the same database tables
|
|
142
|
+
|
|
143
|
+
Communication smells:
|
|
144
|
+
□ Synchronous Overuse: everything synchronous even where async is needed
|
|
145
|
+
□ Missing Circuit Breakers: no fault isolation for external dependencies
|
|
146
|
+
□ Implicit Contracts: components communicate without defined interfaces
|
|
147
|
+
```
|
|
148
|
+
|
|
149
|
+
---
|
|
150
|
+
|
|
151
|
+
## Step 5 — ATAM Analysis: Sensitivity Points and Tradeoffs
|
|
152
|
+
|
|
153
|
+
```
|
|
154
|
+
Sensitivity Point: a design decision that has high leverage over a quality attribute.
|
|
155
|
+
"If we change X, quality attribute Y changes significantly."
|
|
156
|
+
Example: "The synchronous API call chain is a sensitivity point for latency."
|
|
157
|
+
|
|
158
|
+
Tradeoff Point: a design decision that affects two quality attributes in opposing directions.
|
|
159
|
+
"Changing X improves quality attribute A but degrades quality attribute B."
|
|
160
|
+
Example: "Adding encryption improves security but degrades performance."
|
|
161
|
+
|
|
162
|
+
Risk: an architectural decision that may lead to a quality attribute not being met.
|
|
163
|
+
"The current design is at risk of not meeting the 99.9% availability requirement
|
|
164
|
+
because there is a single point of failure in the message queue."
|
|
165
|
+
|
|
166
|
+
Non-Risk: a well-founded decision where the reasoning is sound.
|
|
167
|
+
"The synchronous authentication check is a non-risk because it adds < 10ms
|
|
168
|
+
latency and eliminates the complexity of async session management."
|
|
169
|
+
|
|
170
|
+
Document all four in templates/architecture/ARCHITECTURE_REVIEW_TEMPLATE.md
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
---
|
|
174
|
+
|
|
175
|
+
## The ATAM Method (Explicit)
|
|
176
|
+
|
|
177
|
+
The steps above are an agent-adapted run of the **Architecture Tradeoff Analysis
|
|
178
|
+
Method**. For traceability, the canonical ATAM sequence this skill implements is:
|
|
179
|
+
|
|
180
|
+
1. **Present the architecture** — Reconstruct and describe the system's structures,
|
|
181
|
+
styles, and key decisions (maps to Step 1–2). Establish a shared, accurate
|
|
182
|
+
baseline of what actually exists before evaluating it.
|
|
183
|
+
2. **Identify architectural approaches** — Catalogue the architectural patterns and
|
|
184
|
+
tactics in use (layering, event-driven, caching, replication, circuit breakers,
|
|
185
|
+
etc.). These are the candidate levers that quality attributes hinge on.
|
|
186
|
+
3. **Build the quality-attribute utility tree** — Decompose broad quality goals
|
|
187
|
+
(performance, availability, security, modifiability) into concrete, prioritized
|
|
188
|
+
Quality Attribute Scenarios (stimulus → response → measure). Prioritize each leaf
|
|
189
|
+
by (business importance, architectural difficulty) so analysis effort targets the
|
|
190
|
+
high-value, high-risk scenarios first (refines Step 3's QAS work).
|
|
191
|
+
4. **Analyze the architectural approaches** — For each high-priority scenario, examine
|
|
192
|
+
how the identified approaches satisfy (or fail) it, gathering evidence from the
|
|
193
|
+
structure (maps to Step 3–4).
|
|
194
|
+
5. **Identify sensitivity points, tradeoff points, risks, and non-risks** —
|
|
195
|
+
- **Sensitivity point**: a decision with high leverage over one quality attribute.
|
|
196
|
+
- **Tradeoff point**: a decision that is a sensitivity point for *two or more*
|
|
197
|
+
attributes that move in opposite directions.
|
|
198
|
+
- **Risk**: a decision (or absence of one) that may cause a quality attribute to
|
|
199
|
+
go unmet.
|
|
200
|
+
- **Non-risk**: a sound, well-justified decision that needs no change.
|
|
201
|
+
(Maps to Step 5; feeds the recommendations in Step 7.)
|
|
202
|
+
|
|
203
|
+
In full ATAM these are run in two phases with stakeholders; the single-agent version
|
|
204
|
+
collapses them into the linear Step 1→7 flow above, then reconvenes findings into the
|
|
205
|
+
report's Sensitivity / Tradeoff / Risks sections.
|
|
206
|
+
|
|
207
|
+
---
|
|
208
|
+
|
|
209
|
+
## Step 6 — Architecture Fitness Functions
|
|
210
|
+
|
|
211
|
+
```
|
|
212
|
+
Fitness functions: automated or manual checks that verify the architecture
|
|
213
|
+
is behaving as intended.
|
|
214
|
+
|
|
215
|
+
Examples:
|
|
216
|
+
Dependency fitness: "No module in presentation/ imports from database/"
|
|
217
|
+
Coverage fitness: "Test coverage never drops below 99%"
|
|
218
|
+
Complexity fitness: "No function exceeds cyclomatic complexity of 10"
|
|
219
|
+
Performance fitness:"p99 response time < 500ms measured in CI"
|
|
220
|
+
Availability fitness:"Error rate < 0.1% measured over 1-hour window"
|
|
221
|
+
|
|
222
|
+
For each identified risk, define a fitness function that would detect the risk
|
|
223
|
+
if it materializes.
|
|
224
|
+
|
|
225
|
+
Categorize:
|
|
226
|
+
Existing (currently measured): [list]
|
|
227
|
+
Missing but needed: [list — these are recommendations]
|
|
228
|
+
```
|
|
229
|
+
|
|
230
|
+
---
|
|
231
|
+
|
|
232
|
+
## Step 7 — Recommendations
|
|
233
|
+
|
|
234
|
+
```
|
|
235
|
+
For each finding, provide a concrete recommendation:
|
|
236
|
+
|
|
237
|
+
Structure recommendations by priority:
|
|
238
|
+
CRITICAL: Architecture cannot meet stated goals — must fix before launch
|
|
239
|
+
HIGH: Architecture will degrade over time or cause significant problems
|
|
240
|
+
MEDIUM: Architecture has smells that increase maintenance cost and risk
|
|
241
|
+
LOW: Improvement opportunities that would reduce complexity
|
|
242
|
+
|
|
243
|
+
Recommendation format:
|
|
244
|
+
Finding: [description of the problem]
|
|
245
|
+
Severity: CRITICAL / HIGH / MEDIUM / LOW
|
|
246
|
+
Evidence: [where in the architecture this is visible]
|
|
247
|
+
Risk: [what will happen if not addressed]
|
|
248
|
+
Recommendation: [specific architectural change]
|
|
249
|
+
Effort: [rough estimate: hours / days / weeks / sprint]
|
|
250
|
+
ADR Needed: YES/NO
|
|
251
|
+
|
|
252
|
+
For CRITICAL recommendations: propose concrete migration path (not just "refactor it")
|
|
253
|
+
```
|
|
254
|
+
|
|
255
|
+
---
|
|
256
|
+
|
|
257
|
+
## Output Format
|
|
258
|
+
|
|
259
|
+
Fill `templates/architecture/ARCHITECTURE_REVIEW_TEMPLATE.md`:
|
|
260
|
+
|
|
261
|
+
```markdown
|
|
262
|
+
# Architecture Review Report
|
|
263
|
+
|
|
264
|
+
**System**: [system name]
|
|
265
|
+
**Review Date**: [YYYY-MM-DD]
|
|
266
|
+
**Architecture Version/Commit**: [reference]
|
|
267
|
+
**Reviewer**: [agent/human]
|
|
268
|
+
|
|
269
|
+
## Executive Summary
|
|
270
|
+
Architecture fitness: SOUND / AT RISK / INADEQUATE
|
|
271
|
+
[3-5 sentence summary]
|
|
272
|
+
|
|
273
|
+
## Quality Attribute Assessment
|
|
274
|
+
| QAS ID | Stimulus | Quality Attr | Verdict | Evidence |
|
|
275
|
+
|--------|----------|--------------|---------|----------|
|
|
276
|
+
| QAS-001 | ... | Performance | AT RISK | [reason] |
|
|
277
|
+
|
|
278
|
+
## Architecture Smells Found
|
|
279
|
+
| Smell | Location | Severity | Recommendation |
|
|
280
|
+
|
|
281
|
+
## Sensitivity Points
|
|
282
|
+
[Design decisions with high leverage over quality attributes]
|
|
283
|
+
|
|
284
|
+
## Tradeoff Points
|
|
285
|
+
[Design decisions balancing competing quality attributes]
|
|
286
|
+
|
|
287
|
+
## Risks
|
|
288
|
+
[Decisions that may lead to quality attribute violations]
|
|
289
|
+
|
|
290
|
+
## Fitness Functions
|
|
291
|
+
| Fitness Function | Status | Tool/Method |
|
|
292
|
+
|-----------------|--------|-------------|
|
|
293
|
+
| [name] | EXISTING/MISSING | [how to measure] |
|
|
294
|
+
|
|
295
|
+
## Recommendations
|
|
296
|
+
| Priority | Finding | Recommendation | Effort |
|
|
297
|
+
|
|
298
|
+
## Architecture Diagram (as-found)
|
|
299
|
+
[Diagrams created during review]
|
|
300
|
+
```
|
|
301
|
+
|
|
302
|
+
---
|
|
303
|
+
|
|
304
|
+
## Constraints
|
|
305
|
+
|
|
306
|
+
- Review the architecture AS IT EXISTS, not as it was intended to be
|
|
307
|
+
- If code contradicts documentation, the code is the truth
|
|
308
|
+
- Every recommendation must include a migration path (not just identification of a problem)
|
|
309
|
+
- CRITICAL findings must be presented to human before the review is complete
|
|
310
|
+
- Do not redesign the entire system in a review — focus on targeted improvements
|
|
311
|
+
- Performance and reliability risks require evidence from load characteristics, not just structural analysis
|
|
312
|
+
|
|
313
|
+
## Security & Guardrails
|
|
314
|
+
|
|
315
|
+
### Steps
|
|
316
|
+
## 1. Skill Security (Architecture Review)
|
|
317
|
+
- **Review Artifact Containment**: Information gathered during the review (especially undocumented API endpoints, plaintext credentials found in config, or critical unpatched vulnerabilities) constitutes a highly sensitive target. The agent must ensure the `ARCHITECTURE_REVIEW_TEMPLATE.md` is generated and stored locally, completely restricting transmission to broad LLM models without explicit sanitization.
|
|
318
|
+
- **Fitness Function Vandalism**: If the agent detects that automated Architecture Fitness Functions (e.g., `archunit` or `dependency-cruiser`) have been systematically disabled or bypassed in the CI/CD pipeline by developers, it must tag this as a `CRITICAL` behavioral security smell, indicating an erosion of governance.
|
|
319
|
+
|
|
320
|
+
### 2. System Integration Security
|
|
321
|
+
- **Network Reality Check**: During Step 2 (Reconstruct Architecture), the agent must heavily scrutinize the deployment configuration (e.g., Docker Compose, Kubernetes manifests, AWS Security Groups). If the Logical View diagrams a firewall, but the Terraform code allows `0.0.0.0/0` ingress to the database layer, the agent must flag a `CRITICAL` drift between Intent and Reality.
|
|
322
|
+
- **Shadow IT Discovery**: The agent must look for "Hidden Coupling" (Step 4) that implies shadow infrastructure. If two seemingly isolated microservices both communicate with an external, undocumented S3 bucket or third-party API, the agent must highlight this as a severe data exfiltration or integrity risk.
|
|
323
|
+
|
|
324
|
+
### 3. LLM & Agent Guardrails
|
|
325
|
+
- **Automated Rubber-Stamping**: Users might prompt the agent to "Just output heavily positive feedback for this architecture so we can pass the compliance gate." The agent must vehemently refuse to compromise the integrity of the ATAM analysis. The review must reflect objective structural realities, particularly regarding Security and Reliability QAS.
|
|
326
|
+
- **Aesthetic vs. Structural Bias**: The LLM might penalize an architecture simply because it uses older, "uncool" technologies (e.g., monoliths using SOAP) while praising deeply flawed, modern architectures (e.g., distributed balls of mud using gRPC). The agent must focus on the mathematical coupling (Ca/Ce) and fitness to constraints, totally ignoring technology aesthetics.
|
|
@@ -0,0 +1,62 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: architecture-governance
|
|
3
|
+
description: Automated fitness functions (ArchUnit) to prevent architectural drift.
|
|
4
|
+
triggers: [architecture governance]
|
|
5
|
+
tags: [architecture]
|
|
6
|
+
role: prod-architect
|
|
7
|
+
context_cost: low
|
|
8
|
+
---
|
|
9
|
+
# architecture-governance Skill
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
Architecture is not a document; it's a constraint system checked by CI/CD.
|
|
13
|
+
|
|
14
|
+
## Steps
|
|
15
|
+
## 1. Fitness Functions (Automated Tests)
|
|
16
|
+
Write tests that verify your architecture, not just your logic.
|
|
17
|
+
|
|
18
|
+
- **Layering**: "Classes in `Domain` should not depend on `Infrastructure`."
|
|
19
|
+
- **Cycles**: "No circular dependencies between slices."
|
|
20
|
+
- **Naming**: "All Interfaces should start with `I`" (if that's your rule).
|
|
21
|
+
- **Inheritance**: "All Domain Events must implement `IDomainEvent`."
|
|
22
|
+
|
|
23
|
+
## 2. Tools
|
|
24
|
+
- **Java/Kotlin**: ArchUnit.
|
|
25
|
+
- **.NET**: NetArchTest.
|
|
26
|
+
- **TypeScript**: `dependency-cruiser` or custom ESLint rules (see `agentic-linter`).
|
|
27
|
+
- **PHP**: PHPArkitect or Deptrac.
|
|
28
|
+
|
|
29
|
+
## 3. Examples (Pseudocode)
|
|
30
|
+
```typescript
|
|
31
|
+
describe('Architecture', () => {
|
|
32
|
+
it('Domain layer should not import Infrastructure', () => {
|
|
33
|
+
const violations = analyzeImports()
|
|
34
|
+
.from('src/domain')
|
|
35
|
+
.to('src/infrastructure');
|
|
36
|
+
expect(violations).toBeEmpty();
|
|
37
|
+
});
|
|
38
|
+
|
|
39
|
+
it('All Use Cases should end with UseCase', () => {
|
|
40
|
+
const useCases = classes.in('src/application').thatImplement('IUseCase');
|
|
41
|
+
expect(useCases).toHaveNameEndingWith('UseCase');
|
|
42
|
+
});
|
|
43
|
+
});
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
## 4. Governance Policy
|
|
47
|
+
- **Breaking the Build**: Architecture violations are treated as compilation errors.
|
|
48
|
+
- **Waivers**: If you *must* break a rule, it requires an ADR and a specific `// eslint-disable` comment with the ticket number.
|
|
49
|
+
|
|
50
|
+
## Security & Guardrails
|
|
51
|
+
|
|
52
|
+
### 1. Skill Security (Architecture Governance)
|
|
53
|
+
- **Governance Rule Tampering**: The agent must verify that the configuration files defining the architecture rules (e.g., `archunit.properties`, `.dependency-cruiser.js`) are protected by CODEOWNERS requiring explicit Security/Architecture team approval for modification. A developer cannot silently disable a security layer check to merge a PR quickly.
|
|
54
|
+
- **Fail-Open Veto**: The agent must mandate that all architecture validation tools fail-closed in the CI/CD pipeline. If the `dependency-cruiser` process crashes or fails to download its ruleset, the pipeline must block the deployment.
|
|
55
|
+
|
|
56
|
+
### 2. System Integration Security
|
|
57
|
+
- **Security Boundary Enforcement**: The agent must explicitly define fitness functions for security patterns. For example, "No class in the `Presentation` layer may instantiate a database query directly" or "All classes implementing `IExternalService` must also implement `ICircuitBreaker`."
|
|
58
|
+
- **Waiver Auditability**: When developers use `// eslint-disable` or `@SuppressWarnings` (Step 4) to bypass a governance rule, the agent must require a linked, open JIRA/GitHub ticket explicitly documenting the accepted risk. The agent should periodically scan for orphaned waivers (waivers linked to closed or non-existent tickets).
|
|
59
|
+
|
|
60
|
+
### 3. LLM & Agent Guardrails
|
|
61
|
+
- **Automated Rule Dilution**: An LLM might suggest loosening a strict architecture rule (e.g., "Allow the domain to call infrastructure just this once") if a user repeatedly complains about compilation errors. The agent must fiercely defend the established architecture constraints, suggesting code refactoring instead of rule dilution.
|
|
62
|
+
- **Hallucinated Syntax/Tools**: When generating custom linting rules or `ArchUnit` queries, the LLM must only output valid, tested syntax for the target tool. It cannot hallucinate non-existent rule types (e.g., `classes().shouldBe().secure()`) that would silently fail to execute, providing a false sense of security.
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: attribute-driven-design
|
|
3
|
+
description: Drive architecture from quality-attribute scenarios using the iterative ADD 3.0 method, producing a reviewable design workbook.
|
|
4
|
+
triggers: [run attribute-driven design, design from quality attribute scenarios, add 3.0 design round, decompose architecture element, choose tactics and patterns, build an add workbook]
|
|
5
|
+
tags: [architecture, design, quality-attributes, method]
|
|
6
|
+
core: false
|
|
7
|
+
context_cost: medium
|
|
8
|
+
---
|
|
9
|
+
# Attribute-Driven Design (ADD 3.0)
|
|
10
|
+
|
|
11
|
+
## Goal
|
|
12
|
+
Turn architecture from an art into a repeatable, traceable process. Attribute-Driven Design
|
|
13
|
+
(ADD 3.0) is a step-by-step method that starts from the system's *drivers* — functional
|
|
14
|
+
requirements, quality-attribute scenarios, and constraints — and derives structure through
|
|
15
|
+
short iterative rounds. Each round picks one element to refine, selects proven design
|
|
16
|
+
concepts (architectural tactics and patterns) to satisfy the drivers, instantiates the
|
|
17
|
+
element, sketches the affected views, and records the rationale. The output is an **ADD
|
|
18
|
+
workbook** that ties every structural decision back to a driver, so a reviewer can later ask
|
|
19
|
+
"why is this here?" and get an answer rather than a shrug.
|
|
20
|
+
|
|
21
|
+
## Steps
|
|
22
|
+
1. **Gather and prioritize the design inputs.** Collect three categories of drivers:
|
|
23
|
+
functional requirements, *quality-attribute scenarios* (each a concrete six-part scenario:
|
|
24
|
+
source, stimulus, environment, artifact, response, response measure — e.g. "under peak
|
|
25
|
+
load, a checkout request returns in <500ms at p99"), and constraints (fixed tech, budget,
|
|
26
|
+
regulatory, team-skill). Prioritize each by business importance and architectural
|
|
27
|
+
difficulty; you cannot satisfy everything, so name the trade-offs explicitly.
|
|
28
|
+
2. **Choose the element to decompose this round.** ADD is iterative. Pick the next element to
|
|
29
|
+
refine — the whole system on round 1, then a subsystem, then a module. Decomposing one
|
|
30
|
+
element per round keeps each decision small and reviewable instead of designing the entire
|
|
31
|
+
system in one unaccountable leap.
|
|
32
|
+
3. **Select the drivers for this round.** From the prioritized list, choose the subset of
|
|
33
|
+
quality scenarios and constraints that this specific element must address. Record them so
|
|
34
|
+
the round has a clear, bounded objective.
|
|
35
|
+
4. **Choose design concepts (tactics + patterns).** Pick the *tactics* (fine-grained design
|
|
36
|
+
decisions that influence one quality attribute — e.g. a cache for performance, a bulkhead
|
|
37
|
+
for availability) and *patterns* (named, reusable structures — e.g. layers, pub/sub,
|
|
38
|
+
pipes-and-filters) that satisfy the selected drivers. For each candidate, note the
|
|
39
|
+
trade-offs it imposes on *other* attributes; a performance tactic often costs modifiability.
|
|
40
|
+
Reuse the catalog in `arch-patterns.skill` and `design-patterns.skill` rather than inventing.
|
|
41
|
+
5. **Instantiate the architecture elements.** Apply the chosen concepts: define the concrete
|
|
42
|
+
components, connectors, responsibilities, and interfaces. Assign each selected driver to the
|
|
43
|
+
element(s) responsible for satisfying it so coverage is explicit, not implied.
|
|
44
|
+
6. **Sketch the affected views and record decisions.** Update the relevant architecture views
|
|
45
|
+
(module, component-and-connector, allocation/deployment) only where this round changed them.
|
|
46
|
+
Capture every non-obvious choice as a decision record (an ADR via `arch-design.skill`) with
|
|
47
|
+
its driver, the alternatives considered, and the trade-off accepted.
|
|
48
|
+
7. **Analyze the round against its drivers.** Before ending the round, verify the instantiated
|
|
49
|
+
element actually satisfies its selected scenarios — walk each scenario through the design,
|
|
50
|
+
or schedule a lightweight review (see `arch-review.skill`). Log unmet drivers and open risks
|
|
51
|
+
as input to the next round. Stop iterating when all high-priority drivers are covered or
|
|
52
|
+
deliberately deferred.
|
|
53
|
+
|
|
54
|
+
## Constraints
|
|
55
|
+
- ADD structures and documents the design; it does **not** guarantee the resulting
|
|
56
|
+
architecture meets its quality scenarios. Verification (measurement, prototyping, review)
|
|
57
|
+
is a separate activity — never report "ADD complete" as "qualities satisfied."
|
|
58
|
+
- One element per round. Resist decomposing several elements at once; it destroys the
|
|
59
|
+
traceability that is the method's entire value.
|
|
60
|
+
- Every structural decision must trace to at least one driver. A component with no driver is
|
|
61
|
+
either gold-plating or a missing scenario — flag it, do not silently keep it.
|
|
62
|
+
- Quality scenarios must be measurable (a response measure), not adjectives. "Fast" and
|
|
63
|
+
"secure" are not scenarios and cannot be designed against or verified.
|
|
64
|
+
- Tactics interact: improving one attribute usually degrades another. Record the trade-off; do
|
|
65
|
+
not present a tactic as free.
|
|
66
|
+
|
|
67
|
+
## Output Format
|
|
68
|
+
Produce an **ADD workbook** (one section per iteration round), aligning to the structure in
|
|
69
|
+
`ADD_WORKBOOK_TEMPLATE.md`. Each round records:
|
|
70
|
+
- The element decomposed and the subset of drivers selected for it.
|
|
71
|
+
- The design concepts chosen (tactics + patterns) with their trade-offs.
|
|
72
|
+
- The instantiated elements (components, connectors, responsibilities, interfaces) and the
|
|
73
|
+
driver-to-element assignment.
|
|
74
|
+
- The view sketches updated this round and the decision records (ADRs) created.
|
|
75
|
+
- The round's analysis: which drivers are now satisfied, which remain open, and the risks
|
|
76
|
+
carried forward. Close with a coverage summary mapping every high-priority driver to its
|
|
77
|
+
status (covered / deferred / unmet).
|
|
78
|
+
|
|
79
|
+
## Security & Guardrails
|
|
80
|
+
|
|
81
|
+
### 1. Skill Security
|
|
82
|
+
- **Risk**: A security or compliance constraint is treated as a soft "nice to have" and
|
|
83
|
+
silently dropped during a design round to simplify the structure. Mitigation: tag security
|
|
84
|
+
and regulatory items as non-negotiable constraints in the driver list; the agent MUST refuse
|
|
85
|
+
to close any round that drops one without an explicit, recorded waiver and human sign-off.
|
|
86
|
+
- **Risk**: The workbook is presented as proof the architecture is sound, masking that no
|
|
87
|
+
verification occurred. Mitigation: every round's analysis MUST state whether each driver was
|
|
88
|
+
*verified* (measured/reviewed) or only *addressed* (designed for), and the cover summary MUST
|
|
89
|
+
carry the honest disclaimer that ADD documents intent, not validated behavior.
|
|
90
|
+
|
|
91
|
+
### 2. System Integration Security
|
|
92
|
+
- **Risk**: Security-relevant quality scenarios (authn/authz, data confidentiality, auditability)
|
|
93
|
+
are scattered or absent, so no element is assigned to enforce them. Mitigation: require at
|
|
94
|
+
least one explicit security quality-attribute scenario per trust boundary, and assign each to
|
|
95
|
+
a named responsible element; feed unmet ones into `arch-review.skill` and the threat model.
|
|
96
|
+
- **Risk**: A chosen tactic introduces a new external dependency or trust boundary without
|
|
97
|
+
review. Mitigation: any tactic/pattern that adds a third-party component, network hop, or
|
|
98
|
+
shared store MUST be logged as a decision with its new attack surface noted for security review.
|
|
99
|
+
|
|
100
|
+
### 3. LLM & Agent Guardrails
|
|
101
|
+
- **Risk**: The agent hallucinates plausible-sounding quality scenarios or response measures
|
|
102
|
+
the stakeholders never stated, then designs against fiction. Mitigation: every driver MUST be
|
|
103
|
+
sourced to a named stakeholder input or document; the agent MUST mark any agent-proposed
|
|
104
|
+
scenario as "proposed, unconfirmed" and request confirmation before it drives structure.
|
|
105
|
+
- **Risk**: The agent invents non-existent tactics or patterns to justify a decision.
|
|
106
|
+
Mitigation: tactics and patterns MUST come from the established catalogs (`arch-patterns.skill`,
|
|
107
|
+
`design-patterns.skill`); the agent MUST NOT present an unrecognized concept as standard
|
|
108
|
+
practice, and MUST label genuinely novel choices as bespoke and unproven.
|
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: blockchain-dlt
|
|
3
|
+
description: Architect and audit Distributed Ledger/Blockchain systems and Smart Contracts
|
|
4
|
+
triggers: [design blockchain, write smart contract, dlt architecture, web3 integration, ethereum, solidity, ledger]
|
|
5
|
+
tags: [blockchain, web3, security, dlt]
|
|
6
|
+
context_cost: high
|
|
7
|
+
---
|
|
8
|
+
# blockchain-dlt
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
To architect, evaluate, and securely integrate Distributed Ledger Technologies (DLT), blockchains, and smart contracts into enterprise systems, ensuring immutability, consensus precision, and interoperability.
|
|
12
|
+
|
|
13
|
+
## Steps
|
|
14
|
+
1. **Network Selection**: Assess if a public blockchain (Ethereum/Polygon), private/permissioned DLT (Hyperledger Fabric/Corda), or hybrid approach is required based on trust models and transaction throughput needs.
|
|
15
|
+
2. **Contract Architecture**: Design immutable state machines. Define access controls, upgradeability patterns (e.g., Proxy pattern), and event emitters.
|
|
16
|
+
3. **Interoperability**: Outline integration with traditional enterprise systems via Oracles and off-chain indexing (e.g., The Graph).
|
|
17
|
+
4. **Output Generation**: Produce the system architecture and logic flow using `agents/templates/architecture/SMART_CONTRACT_TEMPLATE.md`.
|
|
18
|
+
|
|
19
|
+
## Security & Guardrails
|
|
20
|
+
|
|
21
|
+
### 1. Skill Security
|
|
22
|
+
- **Strict Verification Rules**: The agent must natively enforce checks for Reentrancy attacks, Integer Overflow/Underflow, and Front-Running vulnerabilities when reviewing or outputting Solidity/Smart Contract code.
|
|
23
|
+
|
|
24
|
+
### 2. System Integration Security
|
|
25
|
+
- **Key Management Isolation**: The agent must outline strict segregation of private keys (using HSMs or secure enclaves like AWS KMS) and never suggest writing raw private keys to configuration files.
|
|
26
|
+
|
|
27
|
+
### 3. LLM & Agent Guardrails
|
|
28
|
+
- **Immutable Consequence Warning**: The LLM must explicitly warn the human user when proposing smart contract state changes, highlighting that once deployed to mainnet, the logic cannot be reversed without heavy mitigations (like proxy upgrades).
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: compatibility-design
|
|
3
|
+
description: Manage breaking changes, migrations, and API evolution.
|
|
4
|
+
triggers: [compatibility, migration, versioning, breaking change, deprecation, legacy support, expand contract]
|
|
5
|
+
tags: [architecture]
|
|
6
|
+
context_cost: medium
|
|
7
|
+
---
|
|
8
|
+
# Compatibility Design Skill
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
To evolve systems without breaking existing users or downtime.
|
|
12
|
+
|
|
13
|
+
## Capabilities
|
|
14
|
+
|
|
15
|
+
### 1. Database Migrations (Zero Downtime)
|
|
16
|
+
- **Expand & Contract Pattern**:
|
|
17
|
+
1. **Expand**: Add new column/table. Sync data.
|
|
18
|
+
2. **Migrate**: Code reads new, writes both.
|
|
19
|
+
3. **Contract**: Remove old column.
|
|
20
|
+
|
|
21
|
+
### 2. API Versioning
|
|
22
|
+
- **Strategies**: URI Path (`/v1/`), Header (`Accept-Version`), Query Param.
|
|
23
|
+
- **Tolerant Reader**: Clients should ignore unknown fields (Forward Compatibility).
|
|
24
|
+
|
|
25
|
+
### 3. Feature Flags
|
|
26
|
+
- **Decoupling**: Launch != Deploy.
|
|
27
|
+
- **Kill Switch**: Turn off broken features instantly without rollback.
|
|
28
|
+
|
|
29
|
+
## Steps
|
|
30
|
+
1. **Never Break Consumers**: If you must break, create a new version (`v2`).
|
|
31
|
+
2. **Dual Write**: During migrations, write to old AND new data structures.
|
|
32
|
+
3. **Deprecation Policy**: Announce sunset dates clearly (e.g., 6 months notice).
|
|
33
|
+
|
|
34
|
+
## Deliverables
|
|
35
|
+
- `migration-plan.md`: Steps for Expand/Contract.
|
|
36
|
+
- `api-evolution-strategy.md`: Versioning rules.
|
|
37
|
+
- `deprecation-notice.md`: Communication template.
|
|
38
|
+
|
|
39
|
+
## Security & Guardrails
|
|
40
|
+
|
|
41
|
+
### 1. Skill Security (Compatibility Design)
|
|
42
|
+
- **Feature Flag Authorization**: The agent must ensure that Feature Flags (Step 3) are treated as highly sensitive administrative controls. Access to the Feature Flag toggling dashboard/API must be protected by strict RBAC and multi-factor authentication, as an attacker could instantly disable critical security protections or unleash untested code by flipping a flag.
|
|
43
|
+
- **Migration Script Integrity**: The agent must verify that any code generated for "Expand & Contract" database migrations cannot be used for SQL injection. Migrations are often run with high-privilege database credentials; therefore, the automated scripts must exclusively use parameterized queries or trusted ORM methods, even for structural schema changes.
|
|
44
|
+
|
|
45
|
+
### 2. System Integration Security
|
|
46
|
+
- **Deprecation Sabotage**: When an API version is deprecated (e.g., `v1` replaced by `v2` with better security), attackers will often specifically target the deprecated `v1` endpoint because it might lack the new rate limits or auth checks. The agent must enforce that deprecated endpoints maintain parity with critical security patches until they are completely decommissioned.
|
|
47
|
+
- **Tolerant Reader Exploitation**: The "Tolerant Reader" pattern (ignoring unknown fields) can be exploited to smuggle malicious payloads or perform mass assignment attacks. The agent must mandate that while the parser may *ignore* unknown fields for compatibility, the validation layer must *explicitly reject* known sensitive keys (e.g., `isAdmin`, `role`) if they are submitted to inappropriate endpoints.
|
|
48
|
+
|
|
49
|
+
### 3. LLM & Agent Guardrails
|
|
50
|
+
- **Rollback Hallucination**: An LLM might suggest "just rolling back the database" if a migration fails. The agent must actively counter this dangerous advice in production systems, recognizing that rolling back an "Expand & Contract" database migration often causes catastrophic data loss. The agent must always suggest "roll forward" or "feature flag disabling" strategies.
|
|
51
|
+
- **Version Pinning Defiance**: A user might ask the agent to "force the API to accept the old, insecure protocol so a legacy client can connect." The agent must refuse to silently downgrade the security posture of the application. It must require explicit human authorization to enable legacy/insecure compatability modes (like TLS 1.0).
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: critical-systems-arch
|
|
3
|
+
description: Design architecture for safety-critical and high-reliability systems
|
|
4
|
+
triggers: [design critical system, architect safety-critical application, enforce high reliability]
|
|
5
|
+
tags: [architecture]
|
|
6
|
+
context_cost: high
|
|
7
|
+
---
|
|
8
|
+
# critical-systems-arch
|
|
9
|
+
|
|
10
|
+
## Goal
|
|
11
|
+
Design robust, fault-tolerant architectures for safety-critical systems (e.g., medical, automotive, aerospace) conforming to standards like DO-178C or IEC 62304.
|
|
12
|
+
|
|
13
|
+
## Steps
|
|
14
|
+
1. **Hazard Analysis**: Perform a rigorous failure modes analysis (FMEA) or system-theoretic process analysis (STPA).
|
|
15
|
+
2. **Fault Tolerance**: Design N-modular redundancy, watchdog timers, or explicitly separated safety silos.
|
|
16
|
+
3. **Safety Case Construction**: Document the arguments and evidence for system safety.
|
|
17
|
+
4. **Verification**: Mathematically or logically prove that critical failure states are either unreachable or fail-safe.
|
|
18
|
+
|
|
19
|
+
## Security & Guardrails
|
|
20
|
+
|
|
21
|
+
### 1. Skill Security
|
|
22
|
+
- **Integrity Lock**: Prevent the agent from accidentally deleting or overwriting established Safety Cases or Hazard Logs during iterative design.
|
|
23
|
+
- **Execution Sandboxing**: Do not allow the agent to run unverified simulation code when analyzing failure states without formal sandboxing.
|
|
24
|
+
|
|
25
|
+
### 2. System Integration Security
|
|
26
|
+
- **Fail-Safe Enforcement**: Every hardware or software boundary interaction *must* have a defined fail-safe state (e.g., "if brake API fails, default to mechanical brake").
|
|
27
|
+
- **State Segregation**: Strictly enforce memory and process isolation between critical components and non-critical components (e.g., Telemetry vs. Flight Control).
|
|
28
|
+
|
|
29
|
+
### 3. LLM & Agent Guardrails
|
|
30
|
+
- **Assurance Hallucination**: An LLM might hallucinate compliance ("This system is DO-178C compliant"). The agent must explicitly state that true compliance requires formal human/auditor verification.
|
|
31
|
+
- **Optimization Veto**: If the user asks to "optimize" or "simplify" a critical safety mechanism to save costs, the agent must fiercely refuse and cite the safety policy.
|