refactor: reorganize repo docs and tooling layout
Consolidate the repository into clearer apps, tools, and layered docs areas so contributors can navigate and maintain it more reliably. Align validation, metadata sync, and CI around the same canonical workflow to reduce drift across local checks and GitHub Actions.
This commit is contained in:
sck_0
464
docs/users/bundles.md
Normal file
464
docs/users/bundles.md
Normal file
@@ -0,0 +1,464 @@
|
||||
# 📦 Antigravity Skill Bundles
|
||||
|
||||
> **Curated collections of skills organized by role and expertise level.** Don't know where to start? Pick a bundle below to get a curated set of skills for your role.
|
||||
|
||||
## 🚀 Quick Start
|
||||
|
||||
1. **Install the repository:**
|
||||
|
||||
```bash
|
||||
npx antigravity-awesome-skills
|
||||
# or clone manually
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
|
||||
```
|
||||
|
||||
2. **Choose your bundle** from the list below based on your role or interests.
|
||||
|
||||
3. **Use skills** by referencing them in your AI assistant:
|
||||
- Claude Code: `>> /skill-name help me...`
|
||||
- Cursor: `@skill-name in chat`
|
||||
- Gemini CLI: `Use skill-name...`
|
||||
- Codex CLI: `Use skill-name...`
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Essentials & Core
|
||||
|
||||
### 🚀 The "Essentials" Starter Pack
|
||||
|
||||
_For everyone. Install these first._
|
||||
|
||||
- [`concise-planning`](../../skills/concise-planning/): Always start with a plan.
|
||||
- [`lint-and-validate`](../../skills/lint-and-validate/): Keep your code clean automatically.
|
||||
- [`git-pushing`](../../skills/git-pushing/): Save your work safely.
|
||||
- [`kaizen`](../../skills/kaizen/): Continuous improvement mindset.
|
||||
- [`systematic-debugging`](../../skills/systematic-debugging/): Debug like a pro.
|
||||
|
||||
---
|
||||
|
||||
## 🛡️ Security & Compliance
|
||||
|
||||
### 🛡️ The "Security Engineer" Pack
|
||||
|
||||
_For pentesting, auditing, and hardening._
|
||||
|
||||
- [`ethical-hacking-methodology`](../../skills/ethical-hacking-methodology/): The Bible of ethical hacking.
|
||||
- [`burp-suite-testing`](../../skills/burp-suite-testing/): Web vulnerability scanning.
|
||||
- [`top-web-vulnerabilities`](../../skills/top-web-vulnerabilities/): OWASP-aligned vulnerability taxonomy.
|
||||
- [`linux-privilege-escalation`](../../skills/linux-privilege-escalation/): Advanced Linux security assessment.
|
||||
- [`cloud-penetration-testing`](../../skills/cloud-penetration-testing/): AWS/Azure/GCP security.
|
||||
- [`security-auditor`](../../skills/security-auditor/): Comprehensive security audits.
|
||||
- [`vulnerability-scanner`](../../skills/vulnerability-scanner/): Advanced vulnerability analysis.
|
||||
|
||||
### 🔐 The "Security Developer" Pack
|
||||
|
||||
_For building secure applications._
|
||||
|
||||
- [`api-security-best-practices`](../../skills/api-security-best-practices/): Secure API design patterns.
|
||||
- [`auth-implementation-patterns`](../../skills/auth-implementation-patterns/): JWT, OAuth2, session management.
|
||||
- [`backend-security-coder`](../../skills/backend-security-coder/): Secure backend coding practices.
|
||||
- [`frontend-security-coder`](../../skills/frontend-security-coder/): XSS prevention and client-side security.
|
||||
- [`cc-skill-security-review`](../../skills/cc-skill-security-review/): Security checklist for features.
|
||||
- [`pci-compliance`](../../skills/pci-compliance/): Payment card security standards.
|
||||
|
||||
---
|
||||
|
||||
## 🌐 Web Development
|
||||
|
||||
### 🌐 The "Web Wizard" Pack
|
||||
|
||||
_For building modern, high-performance web apps._
|
||||
|
||||
- [`frontend-design`](../../skills/frontend-design/): UI guidelines and aesthetics.
|
||||
- [`react-best-practices`](../../skills/react-best-practices/): React & Next.js performance optimization.
|
||||
- [`react-patterns`](../../skills/react-patterns/): Modern React patterns and principles.
|
||||
- [`nextjs-best-practices`](../../skills/nextjs-best-practices/): Next.js App Router patterns.
|
||||
- [`tailwind-patterns`](../../skills/tailwind-patterns/): Tailwind CSS v4 styling superpowers.
|
||||
- [`form-cro`](../../skills/form-cro/): Optimize your forms for conversion.
|
||||
- [`seo-audit`](../../skills/seo-audit/): Get found on Google.
|
||||
|
||||
### 🖌️ The "Web Designer" Pack
|
||||
|
||||
_For pixel-perfect experiences._
|
||||
|
||||
- [`ui-ux-pro-max`](../../skills/ui-ux-pro-max/): Premium design systems and tokens.
|
||||
- [`frontend-design`](../../skills/frontend-design/): The base layer of aesthetics.
|
||||
- [`3d-web-experience`](../../skills/3d-web-experience/): Three.js & React Three Fiber magic.
|
||||
- [`canvas-design`](../../skills/canvas-design/): Static visuals and posters.
|
||||
- [`mobile-design`](../../skills/mobile-design/): Mobile-first design principles.
|
||||
- [`scroll-experience`](../../skills/scroll-experience/): Immersive scroll-driven experiences.
|
||||
|
||||
### ⚡ The "Full-Stack Developer" Pack
|
||||
|
||||
_For end-to-end web application development._
|
||||
|
||||
- [`senior-fullstack`](../../skills/senior-fullstack/): Complete fullstack development guide.
|
||||
- [`frontend-developer`](../../skills/frontend-developer/): React 19+ and Next.js 15+ expertise.
|
||||
- [`backend-dev-guidelines`](../../skills/backend-dev-guidelines/): Node.js/Express/TypeScript patterns.
|
||||
- [`api-patterns`](../../skills/api-patterns/): REST vs GraphQL vs tRPC selection.
|
||||
- [`database-design`](../../skills/database-design/): Schema design and ORM selection.
|
||||
- [`stripe-integration`](../../skills/stripe-integration/): Payments and subscriptions.
|
||||
|
||||
---
|
||||
|
||||
## 🤖 AI & Agents
|
||||
|
||||
### 🤖 The "Agent Architect" Pack
|
||||
|
||||
_For building AI systems and autonomous agents._
|
||||
|
||||
- [`agent-evaluation`](../../skills/agent-evaluation/): Test and benchmark your agents.
|
||||
- [`langgraph`](../../skills/langgraph/): Build stateful agent workflows.
|
||||
- [`mcp-builder`](../../skills/mcp-builder/): Create your own MCP tools.
|
||||
- [`prompt-engineering`](../../skills/prompt-engineering/): Master the art of talking to LLMs.
|
||||
- [`ai-agents-architect`](../../skills/ai-agents-architect/): Design autonomous AI agents.
|
||||
- [`rag-engineer`](../../skills/rag-engineer/): Build RAG systems with vector search.
|
||||
|
||||
### 🧠 The "LLM Application Developer" Pack
|
||||
|
||||
_For building production LLM applications._
|
||||
|
||||
- [`llm-app-patterns`](../../skills/llm-app-patterns/): Production-ready LLM patterns.
|
||||
- [`rag-implementation`](../../skills/rag-implementation/): Retrieval-Augmented Generation.
|
||||
- [`prompt-caching`](../../skills/prompt-caching/): Cache strategies for LLM prompts.
|
||||
- [`context-window-management`](../../skills/context-window-management/): Manage LLM context efficiently.
|
||||
- [`langfuse`](../../skills/langfuse/): LLM observability and tracing.
|
||||
|
||||
---
|
||||
|
||||
## 🎮 Game Development
|
||||
|
||||
### 🎮 The "Indie Game Dev" Pack
|
||||
|
||||
_For building games with AI assistants._
|
||||
|
||||
- [`game-development/game-design`](../../skills/game-development/game-design/): Mechanics and loops.
|
||||
- [`game-development/2d-games`](../../skills/game-development/2d-games/): Sprites and physics.
|
||||
- [`game-development/3d-games`](../../skills/game-development/3d-games/): Models and shaders.
|
||||
- [`unity-developer`](../../skills/unity-developer/): Unity 6 LTS development.
|
||||
- [`godot-gdscript-patterns`](../../skills/godot-gdscript-patterns/): Godot 4 GDScript patterns.
|
||||
- [`algorithmic-art`](../../skills/algorithmic-art/): Generate assets with code.
|
||||
|
||||
---
|
||||
|
||||
## 🐍 Backend & Languages
|
||||
|
||||
### 🐍 The "Python Pro" Pack
|
||||
|
||||
_For backend heavyweights and data scientists._
|
||||
|
||||
- [`python-pro`](../../skills/python-pro/): Master Python 3.12+ with modern features.
|
||||
- [`python-patterns`](../../skills/python-patterns/): Idiomatic Python code.
|
||||
- [`fastapi-pro`](../../skills/fastapi-pro/): High-performance async APIs.
|
||||
- [`fastapi-templates`](../../skills/fastapi-templates/): Production-ready FastAPI projects.
|
||||
- [`django-pro`](../../skills/django-pro/): The battery-included framework.
|
||||
- [`python-testing-patterns`](../../skills/python-testing-patterns/): Comprehensive testing with pytest.
|
||||
- [`async-python-patterns`](../../skills/async-python-patterns/): Python asyncio mastery.
|
||||
|
||||
### 🟦 The "TypeScript & JavaScript" Pack
|
||||
|
||||
_For modern web development._
|
||||
|
||||
- [`typescript-expert`](../../skills/typescript-expert/): TypeScript mastery and advanced types.
|
||||
- [`javascript-pro`](../../skills/javascript-pro/): Modern JavaScript with ES6+.
|
||||
- [`react-best-practices`](../../skills/react-best-practices/): React performance optimization.
|
||||
- [`nodejs-best-practices`](../../skills/nodejs-best-practices/): Node.js development principles.
|
||||
- [`nextjs-app-router-patterns`](../../skills/nextjs-app-router-patterns/): Next.js 14+ App Router.
|
||||
|
||||
### 🦀 The "Systems Programming" Pack
|
||||
|
||||
_For low-level and performance-critical code._
|
||||
|
||||
- [`rust-pro`](../../skills/rust-pro/): Rust 1.75+ with async patterns.
|
||||
- [`go-concurrency-patterns`](../../skills/go-concurrency-patterns/): Go concurrency mastery.
|
||||
- [`golang-pro`](../../skills/golang-pro/): Go development expertise.
|
||||
- [`memory-safety-patterns`](../../skills/memory-safety-patterns/): Memory-safe programming.
|
||||
- [`cpp-pro`](../../skills/cpp-pro/): Modern C++ development.
|
||||
|
||||
---
|
||||
|
||||
## 🦄 Product & Business
|
||||
|
||||
### 🦄 The "Startup Founder" Pack
|
||||
|
||||
_For building products, not just code._
|
||||
|
||||
- [`product-manager-toolkit`](../../skills/product-manager-toolkit/): RICE prioritization, PRD templates.
|
||||
- [`competitive-landscape`](../../skills/competitive-landscape/): Competitor analysis.
|
||||
- [`competitor-alternatives`](../../skills/competitor-alternatives/): Create comparison pages.
|
||||
- [`launch-strategy`](../../skills/launch-strategy/): Product launch planning.
|
||||
- [`copywriting`](../../skills/copywriting/): Marketing copy that converts.
|
||||
- [`stripe-integration`](../../skills/stripe-integration/): Get paid from day one.
|
||||
|
||||
### 📊 The "Business Analyst" Pack
|
||||
|
||||
_For data-driven decision making._
|
||||
|
||||
- [`business-analyst`](../../skills/business-analyst/): AI-powered analytics and KPIs.
|
||||
- [`startup-metrics-framework`](../../skills/startup-metrics-framework/): SaaS metrics and unit economics.
|
||||
- [`startup-financial-modeling`](../../skills/startup-financial-modeling/): 3-5 year financial projections.
|
||||
- [`market-sizing-analysis`](../../skills/market-sizing-analysis/): TAM/SAM/SOM calculations.
|
||||
- [`kpi-dashboard-design`](../../skills/kpi-dashboard-design/): Effective KPI dashboards.
|
||||
|
||||
### 📈 The "Marketing & Growth" Pack
|
||||
|
||||
_For driving user acquisition and retention._
|
||||
|
||||
- [`content-creator`](../../skills/content-creator/): SEO-optimized marketing content.
|
||||
- [`seo-audit`](../../skills/seo-audit/): Technical SEO health checks.
|
||||
- [`programmatic-seo`](../../skills/programmatic-seo/): Create pages at scale.
|
||||
- [`analytics-tracking`](../../skills/analytics-tracking/): Set up GA4/PostHog correctly.
|
||||
- [`ab-test-setup`](../../skills/ab-test-setup/): Validated learning experiments.
|
||||
- [`email-sequence`](../../skills/email-sequence/): Automated email campaigns.
|
||||
|
||||
---
|
||||
|
||||
## 🌧️ DevOps & Infrastructure
|
||||
|
||||
### 🌧️ The "DevOps & Cloud" Pack
|
||||
|
||||
_For infrastructure and scaling._
|
||||
|
||||
- [`docker-expert`](../../skills/docker-expert/): Master containers and multi-stage builds.
|
||||
- [`aws-serverless`](../../skills/aws-serverless/): Serverless on AWS (Lambda, DynamoDB).
|
||||
- [`kubernetes-architect`](../../skills/kubernetes-architect/): K8s architecture and GitOps.
|
||||
- [`terraform-specialist`](../../skills/terraform-specialist/): Infrastructure as Code mastery.
|
||||
- [`environment-setup-guide`](../../skills/environment-setup-guide/): Standardization for teams.
|
||||
- [`deployment-procedures`](../../skills/deployment-procedures/): Safe rollout strategies.
|
||||
- [`bash-linux`](../../skills/bash-linux/): Terminal wizardry.
|
||||
|
||||
### 📊 The "Observability & Monitoring" Pack
|
||||
|
||||
_For production reliability._
|
||||
|
||||
- [`observability-engineer`](../../skills/observability-engineer/): Comprehensive monitoring systems.
|
||||
- [`distributed-tracing`](../../skills/distributed-tracing/): Track requests across microservices.
|
||||
- [`slo-implementation`](../../skills/slo-implementation/): Service Level Objectives.
|
||||
- [`incident-responder`](../../skills/incident-responder/): Rapid incident response.
|
||||
- [`postmortem-writing`](../../skills/postmortem-writing/): Blameless postmortems.
|
||||
- [`performance-engineer`](../../skills/performance-engineer/): Application performance optimization.
|
||||
|
||||
---
|
||||
|
||||
## 📊 Data & Analytics
|
||||
|
||||
### 📊 The "Data & Analytics" Pack
|
||||
|
||||
_For making sense of the numbers._
|
||||
|
||||
- [`analytics-tracking`](../../skills/analytics-tracking/): Set up GA4/PostHog correctly.
|
||||
- [`claude-d3js-skill`](../../skills/claude-d3js-skill/): Beautiful custom visualizations with D3.js.
|
||||
- [`sql-pro`](../../skills/sql-pro/): Modern SQL with cloud-native databases.
|
||||
- [`postgres-best-practices`](../../skills/postgres-best-practices/): Postgres optimization.
|
||||
- [`ab-test-setup`](../../skills/ab-test-setup/): Validated learning.
|
||||
- [`database-architect`](../../skills/database-architect/): Database design from scratch.
|
||||
|
||||
### 🔄 The "Data Engineering" Pack
|
||||
|
||||
_For building data pipelines._
|
||||
|
||||
- [`data-engineer`](../../skills/data-engineer/): Data pipeline architecture.
|
||||
- [`airflow-dag-patterns`](../../skills/airflow-dag-patterns/): Apache Airflow DAGs.
|
||||
- [`dbt-transformation-patterns`](../../skills/dbt-transformation-patterns/): Analytics engineering.
|
||||
- [`vector-database-engineer`](../../skills/vector-database-engineer/): Vector databases for RAG.
|
||||
- [`embedding-strategies`](../../skills/embedding-strategies/): Embedding model selection.
|
||||
|
||||
---
|
||||
|
||||
## 🎨 Creative & Content
|
||||
|
||||
### 🎨 The "Creative Director" Pack
|
||||
|
||||
_For visuals, content, and branding._
|
||||
|
||||
- [`canvas-design`](../../skills/canvas-design/): Generate posters and diagrams.
|
||||
- [`frontend-design`](../../skills/frontend-design/): UI aesthetics.
|
||||
- [`content-creator`](../../skills/content-creator/): SEO-optimized blog posts.
|
||||
- [`copy-editing`](../../skills/copy-editing/): Polish your prose.
|
||||
- [`algorithmic-art`](../../skills/algorithmic-art/): Code-generated masterpieces.
|
||||
- [`interactive-portfolio`](../../skills/interactive-portfolio/): Portfolios that land jobs.
|
||||
|
||||
---
|
||||
|
||||
## 🐞 Quality Assurance
|
||||
|
||||
### 🐞 The "QA & Testing" Pack
|
||||
|
||||
_For breaking things before users do._
|
||||
|
||||
- [`test-driven-development`](../../skills/test-driven-development/): Red, Green, Refactor.
|
||||
- [`systematic-debugging`](../../skills/systematic-debugging/): Debug like Sherlock Holmes.
|
||||
- [`browser-automation`](../../skills/browser-automation/): End-to-end testing with Playwright.
|
||||
- [`e2e-testing-patterns`](../../skills/e2e-testing-patterns/): Reliable E2E test suites.
|
||||
- [`ab-test-setup`](../../skills/ab-test-setup/): Validated experiments.
|
||||
- [`code-review-checklist`](../../skills/code-review-checklist/): Catch bugs in PRs.
|
||||
- [`test-fixing`](../../skills/test-fixing/): Fix failing tests systematically.
|
||||
|
||||
---
|
||||
|
||||
## 🔧 Specialized Packs
|
||||
|
||||
### 📱 The "Mobile Developer" Pack
|
||||
|
||||
_For iOS, Android, and cross-platform apps._
|
||||
|
||||
- [`mobile-developer`](../../skills/mobile-developer/): Cross-platform mobile development.
|
||||
- [`react-native-architecture`](../../skills/react-native-architecture/): React Native with Expo.
|
||||
- [`flutter-expert`](../../skills/flutter-expert/): Flutter multi-platform apps.
|
||||
- [`ios-developer`](../../skills/ios-developer/): iOS development with Swift.
|
||||
- [`app-store-optimization`](../../skills/app-store-optimization/): ASO for App Store and Play Store.
|
||||
|
||||
### 🔗 The "Integration & APIs" Pack
|
||||
|
||||
_For connecting services and building integrations._
|
||||
|
||||
- [`stripe-integration`](../../skills/stripe-integration/): Payments and subscriptions.
|
||||
- [`twilio-communications`](../../skills/twilio-communications/): SMS, voice, WhatsApp.
|
||||
- [`hubspot-integration`](../../skills/hubspot-integration/): CRM integration.
|
||||
- [`plaid-fintech`](../../skills/plaid-fintech/): Bank account linking and ACH.
|
||||
- [`algolia-search`](../../skills/algolia-search/): Search implementation.
|
||||
|
||||
### 🎯 The "Architecture & Design" Pack
|
||||
|
||||
_For system design and technical decisions._
|
||||
|
||||
- [`senior-architect`](../../skills/senior-architect/): Comprehensive software architecture.
|
||||
- [`architecture-patterns`](../../skills/architecture-patterns/): Clean Architecture, DDD, Hexagonal.
|
||||
- [`microservices-patterns`](../../skills/microservices-patterns/): Microservices architecture.
|
||||
- [`event-sourcing-architect`](../../skills/event-sourcing-architect/): Event sourcing and CQRS.
|
||||
- [`architecture-decision-records`](../../skills/architecture-decision-records/): Document technical decisions.
|
||||
|
||||
### 🧱 The "DDD & Evented Architecture" Pack
|
||||
|
||||
_For teams modeling complex domains and evolving toward evented systems._
|
||||
|
||||
- [`domain-driven-design`](../../skills/domain-driven-design/): Route DDD work from strategic modeling to implementation patterns.
|
||||
- [`ddd-strategic-design`](../../skills/ddd-strategic-design/): Subdomains, bounded contexts, and ubiquitous language.
|
||||
- [`ddd-context-mapping`](../../skills/ddd-context-mapping/): Cross-context integration and anti-corruption boundaries.
|
||||
- [`ddd-tactical-patterns`](../../skills/ddd-tactical-patterns/): Aggregates, value objects, repositories, and domain events.
|
||||
- [`cqrs-implementation`](../../skills/cqrs-implementation/): Read/write model separation.
|
||||
- [`event-store-design`](../../skills/event-store-design/): Event persistence and replay architecture.
|
||||
- [`saga-orchestration`](../../skills/saga-orchestration/): Cross-context long-running transaction coordination.
|
||||
- [`projection-patterns`](../../skills/projection-patterns/): Materialized read models from event streams.
|
||||
|
||||
---
|
||||
|
||||
## 🧰 Maintainer & OSS
|
||||
|
||||
### 🛠️ The "OSS Maintainer" Pack
|
||||
|
||||
_For shipping clean changes in public repositories._
|
||||
|
||||
- [`commit`](../../skills/commit/): High-quality conventional commits.
|
||||
- [`create-pr`](../../skills/create-pr/): PR creation with review-ready context.
|
||||
- [`requesting-code-review`](../../skills/requesting-code-review/): Ask for targeted, high-signal reviews.
|
||||
- [`receiving-code-review`](../../skills/receiving-code-review/): Apply feedback with technical rigor.
|
||||
- [`changelog-automation`](../../skills/changelog-automation/): Keep release notes and changelogs consistent.
|
||||
- [`git-advanced-workflows`](../../skills/git-advanced-workflows/): Rebase, cherry-pick, bisect, recovery.
|
||||
- [`documentation-templates`](../../skills/documentation-templates/): Standardize docs and handoffs.
|
||||
|
||||
### 🧱 The "Skill Author" Pack
|
||||
|
||||
_For creating and maintaining high-quality SKILL.md assets._
|
||||
|
||||
- [`skill-creator`](../../skills/skill-creator/): Design effective new skills.
|
||||
- [`skill-developer`](../../skills/skill-developer/): Implement triggers, hooks, and skill lifecycle.
|
||||
- [`writing-skills`](../../skills/writing-skills/): Improve clarity and structure of skill instructions.
|
||||
- [`documentation-generation-doc-generate`](../../skills/documentation-generation-doc-generate/): Generate maintainable technical docs.
|
||||
- [`lint-and-validate`](../../skills/lint-and-validate/): Validate quality after edits.
|
||||
- [`verification-before-completion`](../../skills/verification-before-completion/): Confirm changes before claiming done.
|
||||
|
||||
---
|
||||
|
||||
## 📚 How to Use Bundles
|
||||
|
||||
### 1) Pick by immediate goal
|
||||
|
||||
- Need to ship a feature now: `Essentials` + one domain pack (`Web Wizard`, `Python Pro`, `DevOps & Cloud`).
|
||||
- Need reliability and hardening: add `QA & Testing` + `Security Developer`.
|
||||
- Need product growth: add `Startup Founder` or `Marketing & Growth`.
|
||||
|
||||
### 2) Start with 3-5 skills, not 20
|
||||
|
||||
Pick the minimum set for your current milestone. Expand only when you hit a real gap.
|
||||
|
||||
### 3) Invoke skills consistently
|
||||
|
||||
- **Claude Code**: `>> /skill-name help me...`
|
||||
- **Cursor**: `@skill-name` in chat
|
||||
- **Gemini CLI**: `Use skill-name...`
|
||||
- **Codex CLI**: `Use skill-name...`
|
||||
|
||||
### 4) Build your personal shortlist
|
||||
|
||||
Keep a small list of high-frequency skills and reuse it across tasks to reduce context switching.
|
||||
|
||||
## 🧩 Recommended Bundle Combos
|
||||
|
||||
### Ship a SaaS MVP (2 weeks)
|
||||
|
||||
`Essentials` + `Full-Stack Developer` + `QA & Testing` + `Startup Founder`
|
||||
|
||||
### Harden an existing production app
|
||||
|
||||
`Essentials` + `Security Developer` + `DevOps & Cloud` + `Observability & Monitoring`
|
||||
|
||||
### Build an AI product
|
||||
|
||||
`Essentials` + `Agent Architect` + `LLM Application Developer` + `Data Engineering`
|
||||
|
||||
### Grow traffic and conversions
|
||||
|
||||
`Web Wizard` + `Marketing & Growth` + `Data & Analytics`
|
||||
|
||||
### Launch and maintain open source
|
||||
|
||||
`Essentials` + `OSS Maintainer` + `Architecture & Design`
|
||||
|
||||
---
|
||||
|
||||
## 🎓 Learning Paths
|
||||
|
||||
### Beginner → Intermediate → Advanced
|
||||
|
||||
**Web Development:**
|
||||
|
||||
1. Start: `Essentials` → `Web Wizard`
|
||||
2. Grow: `Full-Stack Developer` → `Architecture & Design`
|
||||
3. Master: `Observability & Monitoring` → `Security Developer`
|
||||
|
||||
**AI/ML:**
|
||||
|
||||
1. Start: `Essentials` → `Agent Architect`
|
||||
2. Grow: `LLM Application Developer` → `Data Engineering`
|
||||
3. Master: Advanced RAG and agent orchestration
|
||||
|
||||
**Security:**
|
||||
|
||||
1. Start: `Essentials` → `Security Developer`
|
||||
2. Grow: `Security Engineer` → Advanced pentesting
|
||||
3. Master: Red team tactics and threat modeling
|
||||
|
||||
**Open Source Maintenance:**
|
||||
|
||||
1. Start: `Essentials` → `OSS Maintainer`
|
||||
2. Grow: `Architecture & Design` → `QA & Testing`
|
||||
3. Master: `Skill Author` + release automation workflows
|
||||
|
||||
---
|
||||
|
||||
## 🤝 Contributing
|
||||
|
||||
Found a skill that should be in a bundle? Or want to create a new bundle? [Open an issue](https://github.com/sickn33/antigravity-awesome-skills/issues) or submit a PR!
|
||||
|
||||
---
|
||||
|
||||
## 📖 Related Documentation
|
||||
|
||||
- [Getting Started Guide](getting-started.md)
|
||||
- [Full Skill Catalog](../../CATALOG.md)
|
||||
- [Contributing Guide](../../CONTRIBUTING.md)
|
||||
|
||||
---
|
||||
|
||||
_Last updated: March 2026 | Total Skills: 1,204+ | Total Bundles: 26_
|
||||
197
docs/users/faq.md
Normal file
197
docs/users/faq.md
Normal file
@@ -0,0 +1,197 @@
|
||||
# ❓ Frequently Asked Questions (FAQ)
|
||||
|
||||
**Got questions?** You're not alone! Here are answers to the most common questions about Antigravity Awesome Skills.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 General Questions
|
||||
|
||||
### What are "skills" exactly?
|
||||
|
||||
Skills are specialized instruction files that teach AI assistants how to handle specific tasks. Think of them as expert knowledge modules that your AI can load on-demand.
|
||||
**Simple analogy:** Just like you might consult different experts (a lawyer, a doctor, a mechanic), these skills let your AI become an expert in different areas when you need them.
|
||||
|
||||
### Do I need to install all 1,204+ skills?
|
||||
|
||||
**No!** When you clone the repository, all skills are available, but your AI only loads them when you explicitly invoke them with `@skill-name`.
|
||||
It's like having a library - all books are there, but you only read the ones you need.
|
||||
**Pro Tip:** Use [Starter Packs](bundles.md) to install only what matches your role.
|
||||
|
||||
### What is the difference between Bundles and Workflows?
|
||||
|
||||
- **Bundles** are curated recommendations grouped by role or domain.
|
||||
- **Workflows** are ordered execution playbooks for concrete outcomes.
|
||||
|
||||
Use bundles when you are deciding _which skills_ to include. Use workflows when you need _step-by-step execution_.
|
||||
|
||||
Start from:
|
||||
|
||||
- [bundles.md](bundles.md)
|
||||
- [workflows.md](workflows.md)
|
||||
|
||||
### Which AI tools work with these skills?
|
||||
|
||||
- ✅ **Claude Code** (Anthropic CLI)
|
||||
- ✅ **Gemini CLI** (Google)
|
||||
- ✅ **Codex CLI** (OpenAI)
|
||||
- ✅ **Cursor** (AI IDE)
|
||||
- ✅ **Antigravity IDE**
|
||||
- ✅ **OpenCode**
|
||||
- ⚠️ **GitHub Copilot** (partial support via copy-paste)
|
||||
|
||||
### Are these skills free to use?
|
||||
|
||||
**Yes!** This repository is licensed under MIT License.
|
||||
|
||||
- ✅ Free for personal use
|
||||
- ✅ Free for commercial use
|
||||
- ✅ You can modify them
|
||||
|
||||
### Do skills work offline?
|
||||
|
||||
The skill files themselves are stored locally on your computer, but your AI assistant needs an internet connection to function.
|
||||
|
||||
---
|
||||
|
||||
## 🔒 Security & Trust (V4 Update)
|
||||
|
||||
### What do the Risk Labels mean?
|
||||
|
||||
We classify skills so you know what you're running:
|
||||
|
||||
- ⚪ **Safe (White/Blue)**: Read-only, planning, or benign skills.
|
||||
- 🔴 **Risk (Red)**: Skills that modify files (delete), use network scanners, or perform destructive actions. **Use with caution.**
|
||||
- 🟣 **Official (Purple)**: Maintained by trusted vendors (Anthropic, DeepMind, etc.).
|
||||
|
||||
### Can these skills hack my computer?
|
||||
|
||||
**No.** Skills are text files. However, they _instruct_ the AI to run commands. If a skill says "delete all files", a compliant AI might try to do it.
|
||||
_Always check the Risk label and review the code._
|
||||
|
||||
---
|
||||
|
||||
## 📦 Installation & Setup
|
||||
|
||||
### Where should I install the skills?
|
||||
|
||||
The universal path that works with most tools is `.agent/skills/`.
|
||||
|
||||
**Using npx:** `npx antigravity-awesome-skills` (or `npx github:sickn33/antigravity-awesome-skills` if you get a 404).
|
||||
|
||||
**Using git clone:**
|
||||
|
||||
```bash
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
|
||||
```
|
||||
|
||||
**Tool-specific paths:**
|
||||
|
||||
- Claude Code: `.claude/skills/`
|
||||
- Gemini CLI: `.gemini/skills/`
|
||||
- Codex CLI: `.codex/skills/`
|
||||
- Cursor: `.cursor/skills/` or project root
|
||||
|
||||
### Does this work with Windows?
|
||||
|
||||
**Yes**, but some "Official" skills use **symlinks** which Windows handles poorly by default.
|
||||
Run git with:
|
||||
|
||||
```bash
|
||||
git clone -c core.symlinks=true https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
|
||||
```
|
||||
|
||||
Or enable "Developer Mode" in Windows Settings.
|
||||
|
||||
### How do I update skills?
|
||||
|
||||
Navigate to your skills directory and pull the latest changes:
|
||||
|
||||
```bash
|
||||
cd .agent/skills
|
||||
git pull origin main
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🛠️ Using Skills
|
||||
|
||||
> **💡 For a complete guide with examples, see [usage.md](usage.md)**
|
||||
|
||||
### How do I invoke a skill?
|
||||
|
||||
Use the `@` symbol followed by the skill name:
|
||||
|
||||
```bash
|
||||
@brainstorming help me design a todo app
|
||||
```
|
||||
|
||||
### Can I use multiple skills at once?
|
||||
|
||||
**Yes!** You can invoke multiple skills:
|
||||
|
||||
```bash
|
||||
@brainstorming help me design this, then use @writing-plans to create a task list.
|
||||
```
|
||||
|
||||
### How do I know which skill to use?
|
||||
|
||||
1. **Browse the catalog**: Check the [Skill Catalog](../../CATALOG.md).
|
||||
2. **Search**: `ls skills/ | grep "keyword"`
|
||||
3. **Ask your AI**: "What skills do you have for testing?"
|
||||
|
||||
---
|
||||
|
||||
## 🏗️ Troubleshooting
|
||||
|
||||
### My AI assistant doesn't recognize skills
|
||||
|
||||
**Possible causes:**
|
||||
|
||||
1. **Wrong installation path**: Check your tool's docs. Try `.agent/skills/`.
|
||||
2. **Restart Needed**: Restart your AI/IDE after installing.
|
||||
3. **Typos**: Did you type `@brain-storming` instead of `@brainstorming`?
|
||||
|
||||
### A skill gives incorrect or outdated advice
|
||||
|
||||
Please [Open an issue](https://github.com/sickn33/antigravity-awesome-skills/issues)!
|
||||
Include:
|
||||
|
||||
- Which skill
|
||||
- What went wrong
|
||||
- What should happen instead
|
||||
|
||||
---
|
||||
|
||||
## 🤝 Contribution
|
||||
|
||||
### I'm new to open source. Can I contribute?
|
||||
|
||||
**Absolutely!** We welcome beginners.
|
||||
|
||||
- Fix typos
|
||||
- Add examples
|
||||
- Improve docs
|
||||
Check out [CONTRIBUTING.md](../../CONTRIBUTING.md) for instructions.
|
||||
|
||||
### My PR failed "Quality Bar" check. Why?
|
||||
|
||||
V4 introduces automated quality control. Your skill might be missing:
|
||||
|
||||
1. A valid `description`.
|
||||
2. Usage examples.
|
||||
Run `npm run validate` locally to check before you push.
|
||||
|
||||
### Can I update an "Official" skill?
|
||||
|
||||
**No.** Official skills (in `skills/official/`) are mirrored from vendors. Open an issue instead.
|
||||
|
||||
---
|
||||
|
||||
## 💡 Pro Tips
|
||||
|
||||
- Start with `@brainstorming` before building anything new
|
||||
- Use `@systematic-debugging` when stuck on bugs
|
||||
- Try `@test-driven-development` for better code quality
|
||||
- Explore `@skill-creator` to make your own skills
|
||||
|
||||
**Still confused?** [Open a discussion](https://github.com/sickn33/antigravity-awesome-skills/discussions) and we'll help you out! 🙌
|
||||
142
docs/users/getting-started.md
Normal file
142
docs/users/getting-started.md
Normal file
@@ -0,0 +1,142 @@
|
||||
# Getting Started with Antigravity Awesome Skills (V7.0.0)
|
||||
|
||||
**New here? This guide will help you supercharge your AI Agent in 5 minutes.**
|
||||
|
||||
> **💡 Confused about what to do after installation?** Check out the [**Complete Usage Guide**](usage.md) for detailed explanations and examples!
|
||||
|
||||
---
|
||||
|
||||
## 🤔 What Are "Skills"?
|
||||
|
||||
AI Agents (like **Claude Code**, **Gemini**, **Cursor**) are smart, but they lack specific knowledge about your tools.
|
||||
**Skills** are specialized instruction manuals (markdown files) that teach your AI how to perform specific tasks perfectly, every time.
|
||||
|
||||
**Analogy:** Your AI is a brilliant intern. **Skills** are the SOPs (Standard Operating Procedures) that make them a Senior Engineer.
|
||||
|
||||
---
|
||||
|
||||
## ⚡️ Quick Start: The "Starter Packs"
|
||||
|
||||
Don't panic about the 1,200+ skills. You don't need them all at once.
|
||||
We have curated **Starter Packs** to get you running immediately.
|
||||
|
||||
You **install the full repo once** (npx or clone); Starter Packs are curated lists to help you **pick which skills to use** by role (e.g. Web Wizard, Hacker Pack)—they are not a different way to install.
|
||||
|
||||
### 1. Install the Repo
|
||||
|
||||
**Option A — npx (easiest):**
|
||||
|
||||
```bash
|
||||
npx antigravity-awesome-skills
|
||||
```
|
||||
|
||||
This clones to `~/.gemini/antigravity/skills` by default. Use `--cursor`, `--claude`, `--gemini`, `--codex`, or `--kiro` to install for a specific tool, or `--path <dir>` for a custom location. Run `npx antigravity-awesome-skills --help` for details.
|
||||
|
||||
If you see a 404 error, use: `npx github:sickn33/antigravity-awesome-skills`
|
||||
|
||||
**Option B — git clone:**
|
||||
|
||||
```bash
|
||||
# Universal (works for most agents)
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills
|
||||
```
|
||||
|
||||
### 2. Pick Your Persona
|
||||
|
||||
Find the bundle that matches your role (see [bundles.md](bundles.md)):
|
||||
|
||||
| Persona | Bundle Name | What's Inside? |
|
||||
| :-------------------- | :------------- | :------------------------------------------------ |
|
||||
| **Web Developer** | `Web Wizard` | React Patterns, Tailwind mastery, Frontend Design |
|
||||
| **Security Engineer** | `Hacker Pack` | OWASP, Metasploit, Pentest Methodology |
|
||||
| **Manager / PM** | `Product Pack` | Brainstorming, Planning, SEO, Strategy |
|
||||
| **Everything** | `Essentials` | Clean Code, Planning, Validation (The Basics) |
|
||||
|
||||
---
|
||||
|
||||
## 🧭 Bundles vs Workflows
|
||||
|
||||
Bundles and workflows solve different problems:
|
||||
|
||||
- **Bundles** = curated sets by role (what to pick).
|
||||
- **Workflows** = step-by-step playbooks (how to execute).
|
||||
|
||||
Start with bundles in [bundles.md](bundles.md), then run a workflow from [workflows.md](workflows.md) when you need guided execution.
|
||||
|
||||
Example:
|
||||
|
||||
> "Use **@antigravity-workflows** and run `ship-saas-mvp` for my project idea."
|
||||
|
||||
---
|
||||
|
||||
## 🚀 How to Use a Skill
|
||||
|
||||
Once installed, just talk to your AI naturally.
|
||||
|
||||
### Example 1: Planning a Feature (**Essentials**)
|
||||
|
||||
> "Use **@brainstorming** to help me design a new login flow."
|
||||
|
||||
**What happens:** The AI loads the brainstorming skill, asks you structured questions, and produces a professional spec.
|
||||
|
||||
### Example 2: Checking Your Code (**Web Wizard**)
|
||||
|
||||
> "Run **@lint-and-validate** on this file and fix errors."
|
||||
|
||||
**What happens:** The AI follows strict linting rules defined in the skill to clean your code.
|
||||
|
||||
### Example 3: Security Audit (**Hacker Pack**)
|
||||
|
||||
> "Use **@api-security-best-practices** to review my API endpoints."
|
||||
|
||||
**What happens:** The AI audits your code against OWASP standards.
|
||||
|
||||
---
|
||||
|
||||
## 🔌 Supported Tools
|
||||
|
||||
| Tool | Status | Path |
|
||||
| :-------------- | :-------------- | :-------------------------------------------------------------------- |
|
||||
| **Claude Code** | ✅ Full Support | `.claude/skills/` |
|
||||
| **Gemini CLI** | ✅ Full Support | `.gemini/skills/` |
|
||||
| **Codex CLI** | ✅ Full Support | `.codex/skills/` |
|
||||
| **Kiro CLI** | ✅ Full Support | Global: `~/.kiro/skills/` · Workspace: `.kiro/skills/` |
|
||||
| **Kiro IDE** | ✅ Full Support | Global: `~/.kiro/skills/` · Workspace: `.kiro/skills/` |
|
||||
| **Antigravity** | ✅ Native | Global: `~/.gemini/antigravity/skills/` · Workspace: `.agent/skills/` |
|
||||
| **Cursor** | ✅ Native | `.cursor/skills/` |
|
||||
| **OpenCode** | ✅ Full Support | `.agents/skills/` |
|
||||
| **AdaL CLI** | ✅ Full Support | `.adal/skills/` |
|
||||
| **Copilot** | ⚠️ Text Only | Manual copy-paste |
|
||||
|
||||
---
|
||||
|
||||
## 🛡️ Trust & Safety (New in V4)
|
||||
|
||||
We classify skills so you know what you're running:
|
||||
|
||||
- 🟣 **Official**: Maintained by Anthropic/Google/Vendors (High Trust).
|
||||
- 🔵 **Safe**: Community skills that are non-destructive (Read-only/Planning).
|
||||
- 🔴 **Risk**: Skills that modify systems or perform security tests (Authorized Use Only).
|
||||
|
||||
_Check the [Skill Catalog](../../CATALOG.md) for the full list._
|
||||
|
||||
---
|
||||
|
||||
## ❓ FAQ
|
||||
|
||||
**Q: Do I need to install all 1,204+ skills?**
|
||||
A: You clone the whole repo once; your AI only _reads_ the skills you invoke (or that are relevant), so it stays lightweight. **Starter Packs** in [bundles.md](bundles.md) are curated lists to help you discover the right skills for your role—they don't change how you install.
|
||||
|
||||
**Q: Can I make my own skills?**
|
||||
A: Yes! Use the **@skill-creator** skill to build your own.
|
||||
|
||||
**Q: Is this free?**
|
||||
A: Yes, MIT License. Open Source forever.
|
||||
|
||||
---
|
||||
|
||||
## ⏭️ Next Steps
|
||||
|
||||
1. [Browse the Bundles](bundles.md)
|
||||
2. [See Real-World Examples](../contributors/examples.md)
|
||||
3. [Contribute a Skill](../../CONTRIBUTING.md)
|
||||
304
docs/users/kiro-integration.md
Normal file
304
docs/users/kiro-integration.md
Normal file
@@ -0,0 +1,304 @@
|
||||
# Kiro CLI Integration Guide
|
||||
|
||||
## Overview
|
||||
|
||||
This guide explains how to use Antigravity Awesome Skills with **Kiro CLI**, AWS's agentic AI-powered coding assistant.
|
||||
|
||||
## What is Kiro?
|
||||
|
||||
Kiro is AWS's agentic AI IDE that combines:
|
||||
|
||||
- **Autonomous coding agents** that work independently for extended periods
|
||||
- **Context-aware assistance** with deep understanding of your codebase
|
||||
- **AWS service integration** with native support for CDK, SAM, and Terraform
|
||||
- **MCP (Model Context Protocol)** for secure external API and database calls
|
||||
- **Spec-driven development** that turns natural language into structured specifications
|
||||
|
||||
## Why Use Skills with Kiro?
|
||||
|
||||
Kiro's agentic capabilities are enhanced by skills that provide:
|
||||
|
||||
- **Domain expertise** across 1,204+ specialized areas
|
||||
- **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
|
||||
- **Workflow automation** for common development tasks
|
||||
- **AWS-specific patterns** for serverless, infrastructure, and cloud architecture
|
||||
|
||||
## Installation
|
||||
|
||||
### Quick Install
|
||||
|
||||
```bash
|
||||
# Install to Kiro's default skills directory
|
||||
npx antigravity-awesome-skills --kiro
|
||||
```
|
||||
|
||||
This installs skills to `~/.kiro/skills/`
|
||||
|
||||
### Manual Installation
|
||||
|
||||
```bash
|
||||
# Clone directly to Kiro's skills directory
|
||||
git clone https://github.com/sickn33/antigravity-awesome-skills.git ~/.kiro/skills
|
||||
```
|
||||
|
||||
### Verification
|
||||
|
||||
```bash
|
||||
# Verify installation
|
||||
test -d ~/.kiro/skills && echo "✓ Skills installed successfully"
|
||||
ls ~/.kiro/skills/skills/ | head -10
|
||||
```
|
||||
|
||||
## Using Skills with Kiro
|
||||
|
||||
### Basic Invocation
|
||||
|
||||
Kiro uses natural language prompts to invoke skills:
|
||||
|
||||
```
|
||||
Use the @brainstorming skill to help me design a serverless API
|
||||
```
|
||||
|
||||
```
|
||||
Apply @aws-serverless patterns to this Lambda function
|
||||
```
|
||||
|
||||
```
|
||||
Run @security-audit on my CDK stack
|
||||
```
|
||||
|
||||
### Recommended Skills for Kiro Users
|
||||
|
||||
#### AWS & Cloud Infrastructure
|
||||
|
||||
- `@aws-serverless` - Serverless architecture patterns
|
||||
- `@aws-cdk` - AWS CDK best practices
|
||||
- `@aws-sam` - SAM template patterns
|
||||
- `@terraform-expert` - Terraform infrastructure as code
|
||||
- `@docker-expert` - Container optimization
|
||||
- `@kubernetes-expert` - K8s deployment patterns
|
||||
|
||||
#### Architecture & Design
|
||||
|
||||
- `@architecture` - System design and ADRs
|
||||
- `@c4-context` - C4 model diagrams
|
||||
- `@senior-architect` - Scalable architecture patterns
|
||||
- `@microservices-patterns` - Microservices design
|
||||
|
||||
#### Security
|
||||
|
||||
- `@api-security-best-practices` - API security hardening
|
||||
- `@vulnerability-scanner` - Security vulnerability detection
|
||||
- `@owasp-top-10` - OWASP security patterns
|
||||
- `@aws-security-best-practices` - AWS security configuration
|
||||
|
||||
#### Development
|
||||
|
||||
- `@typescript-expert` - TypeScript best practices
|
||||
- `@python-patterns` - Python design patterns
|
||||
- `@react-patterns` - React component patterns
|
||||
- `@test-driven-development` - TDD workflows
|
||||
|
||||
#### DevOps & Automation
|
||||
|
||||
- `@ci-cd-pipeline` - CI/CD automation
|
||||
- `@github-actions` - GitHub Actions workflows
|
||||
- `@monitoring-observability` - Observability patterns
|
||||
- `@incident-response` - Incident management
|
||||
|
||||
## Kiro-Specific Workflows
|
||||
|
||||
### 1. Serverless Application Development
|
||||
|
||||
```
|
||||
1. Use @brainstorming to design the application architecture
|
||||
2. Apply @aws-serverless to create Lambda functions
|
||||
3. Use @aws-cdk to generate infrastructure code
|
||||
4. Run @test-driven-development to add tests
|
||||
5. Apply @ci-cd-pipeline to set up deployment
|
||||
```
|
||||
|
||||
### 2. Infrastructure as Code
|
||||
|
||||
```
|
||||
1. Use @architecture to document the system design
|
||||
2. Apply @terraform-expert to write Terraform modules
|
||||
3. Run @security-audit to check for vulnerabilities
|
||||
4. Use @documentation to generate README and runbooks
|
||||
```
|
||||
|
||||
### 3. API Development
|
||||
|
||||
```
|
||||
1. Use @api-design to plan endpoints
|
||||
2. Apply @typescript-expert for implementation
|
||||
3. Run @api-security-best-practices for hardening
|
||||
4. Use @openapi-spec to generate documentation
|
||||
```
|
||||
|
||||
## Advanced Features
|
||||
|
||||
### MCP Integration
|
||||
|
||||
Kiro's MCP support allows skills to:
|
||||
|
||||
- Call external APIs securely
|
||||
- Query databases with context
|
||||
- Integrate with AWS services
|
||||
- Access documentation in real-time
|
||||
|
||||
Skills that leverage MCP:
|
||||
|
||||
- `@rag-engineer` - RAG system implementation
|
||||
- `@langgraph` - Agent workflow orchestration
|
||||
- `@prompt-engineer` - LLM prompt optimization
|
||||
|
||||
### Autonomous Operation
|
||||
|
||||
Kiro can work independently for extended periods. Use skills to guide long-running tasks:
|
||||
|
||||
```
|
||||
Use @systematic-debugging to investigate and fix all TypeScript errors in the codebase,
|
||||
then apply @test-driven-development to add missing tests, and finally run @documentation
|
||||
to update all README files.
|
||||
```
|
||||
|
||||
### Context-Aware Assistance
|
||||
|
||||
Kiro maintains deep context. Reference multiple skills in complex workflows:
|
||||
|
||||
```
|
||||
I'm building a SaaS application. Use @brainstorming for the MVP plan,
|
||||
@aws-serverless for the backend, @react-patterns for the frontend,
|
||||
@stripe-integration for payments, and @security-audit for hardening.
|
||||
```
|
||||
|
||||
## Bundles for Kiro Users
|
||||
|
||||
Pre-curated skill collections optimized for common Kiro use cases:
|
||||
|
||||
### AWS Developer Bundle
|
||||
|
||||
- `@aws-serverless`
|
||||
- `@aws-cdk`
|
||||
- `@aws-sam`
|
||||
- `@lambda-best-practices`
|
||||
- `@dynamodb-patterns`
|
||||
- `@api-gateway-patterns`
|
||||
|
||||
### Full-Stack AWS Bundle
|
||||
|
||||
- `@aws-serverless`
|
||||
- `@react-patterns`
|
||||
- `@typescript-expert`
|
||||
- `@api-design`
|
||||
- `@test-driven-development`
|
||||
- `@ci-cd-pipeline`
|
||||
|
||||
### DevOps & Infrastructure Bundle
|
||||
|
||||
- `@terraform-expert`
|
||||
- `@docker-expert`
|
||||
- `@kubernetes-expert`
|
||||
- `@monitoring-observability`
|
||||
- `@incident-response`
|
||||
- `@security-audit`
|
||||
|
||||
See [bundles.md](bundles.md) for complete bundle listings.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Skills Not Loading
|
||||
|
||||
```bash
|
||||
# Check installation path
|
||||
ls -la ~/.kiro/skills/
|
||||
|
||||
# Reinstall if needed
|
||||
rm -rf ~/.kiro/skills
|
||||
npx antigravity-awesome-skills --kiro
|
||||
```
|
||||
|
||||
### Skill Not Found
|
||||
|
||||
Ensure you're using the correct skill name:
|
||||
|
||||
```bash
|
||||
# List all available skills
|
||||
ls ~/.kiro/skills/skills/
|
||||
```
|
||||
|
||||
### Permission Issues
|
||||
|
||||
```bash
|
||||
# Fix permissions
|
||||
chmod -R 755 ~/.kiro/skills/
|
||||
```
|
||||
|
||||
## Best Practices
|
||||
|
||||
1. **Start with bundles** - Use pre-curated collections for your role
|
||||
2. **Combine skills** - Reference multiple skills in complex tasks
|
||||
3. **Be specific** - Clearly state which skill to use and what to do
|
||||
4. **Iterate** - Let Kiro work autonomously, then refine with additional skills
|
||||
5. **Document** - Use `@documentation` to keep your codebase well-documented
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: Build a Serverless API
|
||||
|
||||
```
|
||||
I need to build a REST API for a todo application using AWS Lambda and DynamoDB.
|
||||
|
||||
Use @brainstorming to design the architecture, then apply @aws-serverless
|
||||
to implement the Lambda functions, @dynamodb-patterns for data modeling,
|
||||
and @api-security-best-practices for security hardening.
|
||||
|
||||
Generate the infrastructure using @aws-cdk and add tests with @test-driven-development.
|
||||
```
|
||||
|
||||
### Example 2: Migrate to Microservices
|
||||
|
||||
```
|
||||
I want to break down this monolithic application into microservices.
|
||||
|
||||
Use @architecture to create an ADR for the migration strategy,
|
||||
apply @microservices-patterns for service boundaries,
|
||||
@docker-expert for containerization, and @kubernetes-expert for orchestration.
|
||||
|
||||
Document the migration plan with @documentation.
|
||||
```
|
||||
|
||||
### Example 3: Security Audit
|
||||
|
||||
```
|
||||
Perform a comprehensive security audit of this application.
|
||||
|
||||
Use @security-audit to scan for vulnerabilities, @owasp-top-10 to check
|
||||
for common issues, @api-security-best-practices for API hardening,
|
||||
and @aws-security-best-practices for cloud configuration.
|
||||
|
||||
Generate a report with findings and remediation steps.
|
||||
```
|
||||
|
||||
## Resources
|
||||
|
||||
- [Kiro Official Documentation](https://kiro.dev)
|
||||
- [AWS Blog: Transform DevOps with Kiro](https://aws.amazon.com/blogs/publicsector/transform-devops-practice-with-kiro-ai-powered-agents/)
|
||||
- [Complete Skills Catalog](../../CATALOG.md)
|
||||
- [Usage Guide](usage.md)
|
||||
- [Workflow Examples](workflows.md)
|
||||
|
||||
## Contributing
|
||||
|
||||
Found a Kiro-specific use case or workflow? Contribute to this guide:
|
||||
|
||||
1. Fork the repository
|
||||
2. Add your examples to this file
|
||||
3. Submit a pull request
|
||||
|
||||
## Support
|
||||
|
||||
- **Issues**: [GitHub Issues](https://github.com/sickn33/antigravity-awesome-skills/issues)
|
||||
- **Discussions**: [GitHub Discussions](https://github.com/sickn33/antigravity-awesome-skills/discussions)
|
||||
- **Community**: [Community Guidelines](../contributors/community-guidelines.md)
|
||||
1722
docs/users/security-skills.md
Normal file
1722
docs/users/security-skills.md
Normal file
File diff suppressed because it is too large
Load Diff
394
docs/users/usage.md
Normal file
394
docs/users/usage.md
Normal file
@@ -0,0 +1,394 @@
|
||||
# 📖 Usage Guide: How to Actually Use These Skills
|
||||
|
||||
> **Confused after installation?** This guide walks you through exactly what to do next, step by step.
|
||||
|
||||
---
|
||||
|
||||
## 🤔 "I just installed the repository. Now what?"
|
||||
|
||||
Great question! Here's what just happened and what to do next:
|
||||
|
||||
### What You Just Did
|
||||
|
||||
When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
|
||||
|
||||
✅ **Downloaded 1,204+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or `~/.agent/skills/` if you used `--path`)
|
||||
✅ **Made them available** to your AI assistant
|
||||
❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
|
||||
|
||||
Think of it like installing a toolbox. You have all the tools now, but you need to **pick which ones to use** for each job.
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Step 1: Understanding "Bundles" (This is NOT Another Install!)
|
||||
|
||||
**Common confusion:** "Do I need to download each skill separately?"
|
||||
|
||||
**Answer: NO!** Here's what bundles actually are:
|
||||
|
||||
### What Bundles Are
|
||||
|
||||
Bundles are **recommended lists** of skills grouped by role. They help you decide which skills to start using.
|
||||
|
||||
**Analogy:**
|
||||
|
||||
- You installed a toolbox with 1,204+ tools (✅ done)
|
||||
- Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
|
||||
- You don't install bundles—you **pick skills from them**
|
||||
|
||||
### What Bundles Are NOT
|
||||
|
||||
❌ Separate installations
|
||||
❌ Different download commands
|
||||
❌ Something you need to "activate"
|
||||
|
||||
### Example: The "Web Wizard" Bundle
|
||||
|
||||
When you see the [Web Wizard bundle](bundles.md#-the-web-wizard-pack), it lists:
|
||||
|
||||
- `frontend-design`
|
||||
- `react-best-practices`
|
||||
- `tailwind-patterns`
|
||||
- etc.
|
||||
|
||||
These are **recommendations** for which skills a web developer should try first. They're already installed—you just need to **use them in your prompts**.
|
||||
|
||||
---
|
||||
|
||||
## 🚀 Step 2: How to Actually Execute/Use a Skill
|
||||
|
||||
This is the part that should have been explained better! Here's how to use skills:
|
||||
|
||||
### The Simple Answer
|
||||
|
||||
**Just mention the skill name in your conversation with your AI assistant.**
|
||||
|
||||
### Different Tools, Different Syntax
|
||||
|
||||
The exact syntax varies by tool, but it's always simple:
|
||||
|
||||
#### Claude Code (CLI)
|
||||
|
||||
```bash
|
||||
# In your terminal/chat with Claude Code:
|
||||
>> Use @brainstorming to help me design a todo app
|
||||
```
|
||||
|
||||
#### Cursor (IDE)
|
||||
|
||||
```bash
|
||||
# In the Cursor chat panel:
|
||||
@brainstorming help me design a todo app
|
||||
```
|
||||
|
||||
#### Gemini CLI
|
||||
|
||||
```bash
|
||||
# In your conversation with Gemini:
|
||||
Use the brainstorming skill to help me plan my app
|
||||
```
|
||||
|
||||
#### Codex CLI
|
||||
|
||||
```bash
|
||||
# In your conversation with Codex:
|
||||
Apply @brainstorming to design a new feature
|
||||
```
|
||||
|
||||
#### Antigravity IDE
|
||||
|
||||
```bash
|
||||
# In agent mode:
|
||||
Use @brainstorming to plan this feature
|
||||
```
|
||||
|
||||
> **Pro Tip:** Most modern tools use the `@skill-name` syntax. When in doubt, try that first!
|
||||
|
||||
---
|
||||
|
||||
## 💬 Step 3: What Should My Prompts Look Like?
|
||||
|
||||
Here are **real-world examples** of good prompts:
|
||||
|
||||
### Example 1: Starting a New Project
|
||||
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Help me build a todo app"
|
||||
|
||||
**Good Prompt:**
|
||||
|
||||
> "Use @brainstorming to help me design a todo app with user authentication and cloud sync"
|
||||
|
||||
**Why it's better:** You're explicitly invoking the skill and providing context.
|
||||
|
||||
---
|
||||
|
||||
### Example 2: Reviewing Code
|
||||
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Check my code"
|
||||
|
||||
**Good Prompt:**
|
||||
|
||||
> "Use @lint-and-validate to check `src/components/Button.tsx` for issues"
|
||||
|
||||
**Why it's better:** Specific skill + specific file = precise results.
|
||||
|
||||
---
|
||||
|
||||
### Example 3: Security Audit
|
||||
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Make my API secure"
|
||||
|
||||
**Good Prompt:**
|
||||
|
||||
> "Use @api-security-best-practices to review my REST endpoints in `routes/api/users.js`"
|
||||
|
||||
**Why it's better:** The AI knows exactly which skill's standards to apply.
|
||||
|
||||
---
|
||||
|
||||
### Example 4: Combining Multiple Skills
|
||||
|
||||
**Good Prompt:**
|
||||
|
||||
> "Use @brainstorming to design a payment flow, then apply @stripe-integration to implement it"
|
||||
|
||||
**Why it's good:** You can chain skills together in a single prompt!
|
||||
|
||||
---
|
||||
|
||||
## 🎓 Step 4: Your First Skill (Hands-On Tutorial)
|
||||
|
||||
Let's actually use a skill right now. Follow these steps:
|
||||
|
||||
### Scenario: You want to plan a new feature
|
||||
|
||||
1. **Pick a skill:** Let's use `brainstorming` (from the "Essentials" bundle)
|
||||
|
||||
2. **Open your AI assistant** (Claude Code, Cursor, etc.)
|
||||
|
||||
3. **Type this exact prompt:**
|
||||
|
||||
```
|
||||
Use @brainstorming to help me design a user profile page for my app
|
||||
```
|
||||
|
||||
4. **Press Enter**
|
||||
|
||||
5. **What happens next:**
|
||||
- The AI loads the brainstorming skill
|
||||
- It will start asking you structured questions (one at a time)
|
||||
- It will guide you through understanding, requirements, and design
|
||||
- You answer each question, and it builds a complete spec
|
||||
|
||||
6. **Result:** You'll end up with a detailed design document—without writing a single line of code yet!
|
||||
|
||||
---
|
||||
|
||||
## 🗂️ Step 5: Picking Your First Skills (Practical Advice)
|
||||
|
||||
Don't try to use all 1,204+ skills at once. Here's a sensible approach:
|
||||
|
||||
### Start with "The Essentials" (5 skills, everyone needs these)
|
||||
|
||||
1. **`@brainstorming`** - Plan before you build
|
||||
2. **`@lint-and-validate`** - Keep code clean
|
||||
3. **`@git-pushing`** - Save work safely
|
||||
4. **`@systematic-debugging`** - Fix bugs faster
|
||||
5. **`@concise-planning`** - Organize tasks
|
||||
|
||||
**How to use them:**
|
||||
|
||||
- Before writing new code → `@brainstorming`
|
||||
- After writing code → `@lint-and-validate`
|
||||
- Before committing → `@git-pushing`
|
||||
- When stuck → `@systematic-debugging`
|
||||
|
||||
### Then Add Role-Specific Skills (5-10 more)
|
||||
|
||||
Find your role in [bundles.md](bundles.md) and pick 5-10 skills from that bundle.
|
||||
|
||||
**Example for Web Developer:**
|
||||
|
||||
- `@frontend-design`
|
||||
- `@react-best-practices`
|
||||
- `@tailwind-patterns`
|
||||
- `@seo-audit`
|
||||
|
||||
**Example for Security Engineer:**
|
||||
|
||||
- `@api-security-best-practices`
|
||||
- `@vulnerability-scanner`
|
||||
- `@ethical-hacking-methodology`
|
||||
|
||||
### Finally, Add On-Demand Skills (as needed)
|
||||
|
||||
Keep the [CATALOG.md](../../CATALOG.md) open as reference. When you need something specific:
|
||||
|
||||
> "I need to integrate Stripe payments"
|
||||
> → Search catalog → Find `@stripe-integration` → Use it!
|
||||
|
||||
---
|
||||
|
||||
## 🔄 Complete Example: Building a Feature End-to-End
|
||||
|
||||
Let's walk through a realistic scenario:
|
||||
|
||||
### Task: "Add a blog to my Next.js website"
|
||||
|
||||
#### Step 1: Plan (use @brainstorming)
|
||||
|
||||
```
|
||||
You: Use @brainstorming to design a blog system for my Next.js site
|
||||
|
||||
AI: [Asks structured questions about requirements]
|
||||
You: [Answer questions]
|
||||
AI: [Produces detailed design spec]
|
||||
```
|
||||
|
||||
#### Step 2: Implement (use @nextjs-best-practices)
|
||||
|
||||
```
|
||||
You: Use @nextjs-best-practices to scaffold the blog with App Router
|
||||
|
||||
AI: [Creates file structure, sets up routes, adds components]
|
||||
```
|
||||
|
||||
#### Step 3: Style (use @tailwind-patterns)
|
||||
|
||||
```
|
||||
You: Use @tailwind-patterns to make the blog posts look modern
|
||||
|
||||
AI: [Applies Tailwind styling with responsive design]
|
||||
```
|
||||
|
||||
#### Step 4: SEO (use @seo-audit)
|
||||
|
||||
```
|
||||
You: Use @seo-audit to optimize the blog for search engines
|
||||
|
||||
AI: [Adds meta tags, sitemaps, structured data]
|
||||
```
|
||||
|
||||
#### Step 5: Test & Deploy
|
||||
|
||||
```
|
||||
You: Use @test-driven-development to add tests, then @vercel-deployment to deploy
|
||||
|
||||
AI: [Creates tests, sets up CI/CD, deploys to Vercel]
|
||||
```
|
||||
|
||||
**Result:** Professional blog built with best practices, without manually researching each step!
|
||||
|
||||
---
|
||||
|
||||
## 🆘 Common Questions
|
||||
|
||||
### "Which tool should I use? Claude Code, Cursor, Gemini?"
|
||||
|
||||
**Any of them!** Skills work universally. Pick the tool you already use or prefer:
|
||||
|
||||
- **Claude Code** - Best for terminal/CLI workflows
|
||||
- **Cursor** - Best for IDE integration
|
||||
- **Gemini CLI** - Best for Google ecosystem
|
||||
- **Codex CLI** - Best for OpenAI ecosystem
|
||||
|
||||
### "Can I see all available skills?"
|
||||
|
||||
Yes! Three ways:
|
||||
|
||||
1. Browse [CATALOG.md](../../CATALOG.md) (searchable list)
|
||||
2. Run `ls ~/.agent/skills/` (if installed there)
|
||||
3. Ask your AI: "What skills do you have for [topic]?"
|
||||
|
||||
### "Do I need to restart my IDE after installing?"
|
||||
|
||||
Usually no, but if your AI doesn't recognize a skill:
|
||||
|
||||
1. Try restarting your IDE/CLI
|
||||
2. Check the installation path matches your tool
|
||||
3. Try the explicit path: `npx antigravity-awesome-skills --claude` (or `--cursor`, `--gemini`, etc.)
|
||||
|
||||
### "Can I create my own skills?"
|
||||
|
||||
Yes! Use the `@skill-creator` skill:
|
||||
|
||||
```
|
||||
Use @skill-creator to help me build a custom skill for [your task]
|
||||
```
|
||||
|
||||
### "What if a skill doesn't work as expected?"
|
||||
|
||||
1. Check the skill's SKILL.md file directly: `~/.agent/skills/[skill-name]/SKILL.md`
|
||||
2. Read the description to ensure you're using it correctly
|
||||
3. [Open an issue](https://github.com/sickn33/antigravity-awesome-skills/issues) with details
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Quick Reference Card
|
||||
|
||||
**Save this for quick lookup:**
|
||||
|
||||
| Task | Skill to Use | Example Prompt |
|
||||
| ---------------- | ------------------------------ | --------------------------------------------------- |
|
||||
| Plan new feature | `@brainstorming` | `Use @brainstorming to design a login system` |
|
||||
| Review code | `@lint-and-validate` | `Use @lint-and-validate on src/app.js` |
|
||||
| Debug issue | `@systematic-debugging` | `Use @systematic-debugging to fix login error` |
|
||||
| Security audit | `@api-security-best-practices` | `Use @api-security-best-practices on my API routes` |
|
||||
| SEO check | `@seo-audit` | `Use @seo-audit on my landing page` |
|
||||
| React component | `@react-patterns` | `Use @react-patterns to build a form component` |
|
||||
| Deploy app | `@vercel-deployment` | `Use @vercel-deployment to ship this to production` |
|
||||
|
||||
---
|
||||
|
||||
## 🚦 Next Steps
|
||||
|
||||
Now that you understand how to use skills:
|
||||
|
||||
1. ✅ **Try one skill right now** - Start with `@brainstorming` on any idea you have
|
||||
2. 📚 **Pick 3-5 skills** from your role's bundle in [bundles.md](bundles.md)
|
||||
3. 🔖 **Bookmark** [CATALOG.md](../../CATALOG.md) for when you need something specific
|
||||
4. 🎯 **Try a workflow** from [workflows.md](workflows.md) for a complete end-to-end process
|
||||
|
||||
---
|
||||
|
||||
## 💡 Pro Tips for Maximum Effectiveness
|
||||
|
||||
### Tip 1: Start Every Feature with @brainstorming
|
||||
|
||||
> Before writing code, use `@brainstorming` to plan. You'll save hours of refactoring.
|
||||
|
||||
### Tip 2: Chain Skills in Order
|
||||
|
||||
> Don't try to do everything at once. Use skills sequentially: Plan → Build → Test → Deploy
|
||||
|
||||
### Tip 3: Be Specific in Prompts
|
||||
|
||||
> Bad: "Use @react-patterns"
|
||||
> Good: "Use @react-patterns to build a modal component with animations"
|
||||
|
||||
### Tip 4: Reference File Paths
|
||||
|
||||
> Help the AI focus: "Use @security-auditor on routes/api/auth.js"
|
||||
|
||||
### Tip 5: Combine Skills for Complex Tasks
|
||||
|
||||
> "Use @brainstorming to design, then @test-driven-development to implement with tests"
|
||||
|
||||
---
|
||||
|
||||
## 📞 Still Confused?
|
||||
|
||||
If something still doesn't make sense:
|
||||
|
||||
1. Check the [FAQ](faq.md)
|
||||
2. See [Real-World Examples](../contributors/examples.md)
|
||||
3. [Open a Discussion](https://github.com/sickn33/antigravity-awesome-skills/discussions)
|
||||
4. [File an Issue](https://github.com/sickn33/antigravity-awesome-skills/issues) to help us improve this guide!
|
||||
|
||||
Remember: You're not alone! The whole point of this project is to make AI assistants easier to use. If this guide didn't help, let us know so we can fix it. 🙌
|
||||
509
docs/users/visual-guide.md
Normal file
509
docs/users/visual-guide.md
Normal file
@@ -0,0 +1,509 @@
|
||||
# Visual Quick Start Guide
|
||||
|
||||
**Learn by seeing!** This guide uses diagrams and visual examples to help you understand skills.
|
||||
|
||||
---
|
||||
|
||||
## The Big Picture
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ YOU (Developer) │
|
||||
│ ↓ │
|
||||
│ "Help me build a payment system" │
|
||||
│ ↓ │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ AI ASSISTANT │
|
||||
│ ↓ │
|
||||
│ Loads @stripe-integration skill │
|
||||
│ ↓ │
|
||||
│ Becomes an expert in Stripe payments │
|
||||
│ ↓ │
|
||||
│ Provides specialized help with code examples │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📦 Repository Structure (Visual)
|
||||
|
||||
```
|
||||
antigravity-awesome-skills/
|
||||
│
|
||||
├── 📄 README.md ← Overview and quick start
|
||||
├── 📄 CONTRIBUTING.md ← Contributor workflow
|
||||
├── 📄 CATALOG.md ← Full generated catalog
|
||||
│
|
||||
├── 📁 skills/ ← 1,204+ skills live here
|
||||
│ │
|
||||
│ ├── 📁 brainstorming/
|
||||
│ │ └── 📄 SKILL.md ← Skill definition
|
||||
│ │
|
||||
│ ├── 📁 stripe-integration/
|
||||
│ │ ├── 📄 SKILL.md
|
||||
│ │ └── 📁 examples/ ← Optional extras
|
||||
│ │
|
||||
│ ├── 📁 game-development/
|
||||
│ │ └── 📁 2d-games/
|
||||
│ │ └── 📄 SKILL.md ← Nested skills also supported
|
||||
│ │
|
||||
│ └── ... (1,200+ total)
|
||||
│
|
||||
├── 📁 apps/
|
||||
│ └── 📁 web-app/ ← Interactive browser
|
||||
│
|
||||
├── 📁 tools/
|
||||
│ ├── 📁 scripts/ ← Validators and generators
|
||||
│ ├── 📁 lib/ ← Shared helpers
|
||||
│ └── 📁 bin/ ← Installer entrypoint
|
||||
│
|
||||
└── 📁 docs/
|
||||
├── 📁 users/ ← Getting started, bundles, workflows
|
||||
├── 📁 contributors/ ← Template, anatomy, quality bar
|
||||
├── 📁 maintainers/ ← Release and maintenance docs
|
||||
└── 📁 sources/ ← Attribution and licenses
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## How Skills Work (Flow Diagram)
|
||||
|
||||
```
|
||||
┌──────────────┐
|
||||
│ 1. INSTALL │ Copy skills to .agent/skills/
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 2. INVOKE │ Type: @skill-name in AI chat
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 3. LOAD │ AI reads SKILL.md file
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 4. EXECUTE │ AI follows skill instructions
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 5. RESULT │ You get specialized help!
|
||||
└──────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Skill Categories (Visual Map)
|
||||
|
||||
```
|
||||
┌─────────────────────────┐
|
||||
│ 1,204+ SKILLS │
|
||||
└────────────┬────────────┘
|
||||
│
|
||||
┌────────────────────────┼────────────────────────┐
|
||||
│ │ │
|
||||
┌────▼────┐ ┌──────▼──────┐ ┌──────▼──────┐
|
||||
│ PRODUCT │ │ DEVELOPMENT │ │ SECURITY │
|
||||
│ & UX │ │ & TESTING │ │ & RELIAB. │
|
||||
└────┬────┘ └──────┬──────┘ └──────┬──────┘
|
||||
│ │ │
|
||||
• Brainstorming • React / Next.js • AppSec reviews
|
||||
• Design systems • TDD / debugging • Pentest guides
|
||||
• Copywriting • API / backend • Cloud hardening
|
||||
• Incident response
|
||||
│ │ │
|
||||
└────────────────────────┼────────────────────────┘
|
||||
│
|
||||
┌────────────────────────┼────────────────────────┐
|
||||
│ │ │
|
||||
┌────▼────┐ ┌──────▼──────┐ ┌──────▼──────┐
|
||||
│ AI │ │ DATA / OPS │ │ DOCS / OSS │
|
||||
│ AGENTS │ │ & CLOUD │ │ MAINTENANCE │
|
||||
└────┬────┘ └──────┬──────┘ └──────┬──────┘
|
||||
│ │ │
|
||||
• RAG systems • SQL / analytics • Release flow
|
||||
• LangGraph • Docker / K8s • Changelog
|
||||
• Prompt engineering • Terraform / AWS • PR / review
|
||||
• Tooling / MCP • Observability • Skill authoring
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Skill File Anatomy (Visual)
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────┐
|
||||
│ SKILL.md │
|
||||
├─────────────────────────────────────────────────────────┤
|
||||
│ │
|
||||
│ ┌───────────────────────────────────────────────┐ │
|
||||
│ │ FRONTMATTER (Metadata) │ │
|
||||
│ │ ───────────────────────────────────────────── │ │
|
||||
│ │ --- │ │
|
||||
│ │ name: my-skill │ │
|
||||
│ │ description: "What this skill does" │ │
|
||||
│ │ --- │ │
|
||||
│ └───────────────────────────────────────────────┘ │
|
||||
│ │
|
||||
│ ┌───────────────────────────────────────────────┐ │
|
||||
│ │ CONTENT (Instructions) │ │
|
||||
│ │ ───────────────────────────────────────────── │ │
|
||||
│ │ │ │
|
||||
│ │ # Skill Title │ │
|
||||
│ │ │ │
|
||||
│ │ ## Overview │ │
|
||||
│ │ What this skill does... │ │
|
||||
│ │ │ │
|
||||
│ │ ## When to Use │ │
|
||||
│ │ - Use when... │ │
|
||||
│ │ │ │
|
||||
│ │ ## Instructions │ │
|
||||
│ │ 1. First step... │ │
|
||||
│ │ 2. Second step... │ │
|
||||
│ │ │ │
|
||||
│ │ ## Examples │ │
|
||||
│ │ ```javascript │ │
|
||||
│ │ // Example code │ │
|
||||
│ │ ``` │ │
|
||||
│ │ │ │
|
||||
│ └───────────────────────────────────────────────┘ │
|
||||
│ │
|
||||
└─────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Installation (Visual Steps)
|
||||
|
||||
### Step 1: Clone the Repository
|
||||
```
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Terminal │
|
||||
├─────────────────────────────────────────┤
|
||||
│ $ git clone https://github.com/ │
|
||||
│ sickn33/antigravity-awesome-skills │
|
||||
│ .agent/skills │
|
||||
│ │
|
||||
│ ✓ Cloning into '.agent/skills'... │
|
||||
│ ✓ Done! │
|
||||
└─────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
### Step 2: Verify Installation
|
||||
```
|
||||
┌─────────────────────────────────────────┐
|
||||
│ File Explorer │
|
||||
├─────────────────────────────────────────┤
|
||||
│ 📁 .agent/ │
|
||||
│ └── 📁 skills/ │
|
||||
│ ├── 📁 brainstorming/ │
|
||||
│ ├── 📁 stripe-integration/ │
|
||||
│ ├── 📁 react-best-practices/ │
|
||||
│ └── ... (1,200+ total) │
|
||||
└─────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
### Step 3: Use a Skill
|
||||
```
|
||||
┌─────────────────────────────────────────┐
|
||||
│ AI Assistant Chat │
|
||||
├─────────────────────────────────────────┤
|
||||
│ You: @brainstorming help me design │
|
||||
│ a todo app │
|
||||
│ │
|
||||
│ AI: Great! Let me help you think │
|
||||
│ through this. First, let's │
|
||||
│ understand your requirements... │
|
||||
│ │
|
||||
│ What's the primary use case? │
|
||||
│ a) Personal task management │
|
||||
│ b) Team collaboration │
|
||||
│ c) Project planning │
|
||||
└─────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Example: Using a Skill (Step-by-Step)
|
||||
|
||||
### Scenario: You want to add Stripe payments to your app
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ STEP 1: Identify the Need │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ "I need to add payment processing to my app" │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ STEP 2: Find the Right Skill │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ Search: "payment" or "stripe" │
|
||||
│ Found: @stripe-integration │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ STEP 3: Invoke the Skill │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ You: @stripe-integration help me add subscription billing │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ STEP 4: AI Loads Skill Knowledge │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ • Stripe API patterns │
|
||||
│ • Webhook handling │
|
||||
│ • Subscription management │
|
||||
│ • Best practices │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
↓
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ STEP 5: Get Expert Help │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ AI provides: │
|
||||
│ • Code examples │
|
||||
│ • Setup instructions │
|
||||
│ • Security considerations │
|
||||
│ • Testing strategies │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Finding Skills (Visual Guide)
|
||||
|
||||
### Method 1: Browse by Category
|
||||
```
|
||||
README.md → Scroll to "Full Skill Registry" → Find category → Pick skill
|
||||
```
|
||||
|
||||
### Method 2: Search by Keyword
|
||||
```
|
||||
Terminal → ls skills/ | grep "keyword" → See matching skills
|
||||
```
|
||||
|
||||
### Method 3: Use the Index
|
||||
```
|
||||
Open skills_index.json → Search for keyword → Find skill path
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Creating Your First Skill (Visual Workflow)
|
||||
|
||||
```
|
||||
┌──────────────┐
|
||||
│ 1. IDEA │ "I want to share my Docker knowledge"
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 2. CREATE │ mkdir skills/docker-mastery
|
||||
└──────┬───────┘ touch skills/docker-mastery/SKILL.md
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 3. WRITE │ Add frontmatter + content
|
||||
└──────┬───────┘ (Use docs/contributors/skill-template.md)
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 4. TEST │ Copy to .agent/skills/
|
||||
└──────┬───────┘ Try: @docker-mastery
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 5. VALIDATE │ npm run validate
|
||||
└──────┬───────┘
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 6. SUBMIT │ git commit + push + Pull Request
|
||||
└──────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Skill Complexity Levels
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ SKILL COMPLEXITY │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ │
|
||||
│ SIMPLE STANDARD COMPLEX │
|
||||
│ ────── ──────── ─────── │
|
||||
│ │
|
||||
│ • 1 file • 1 file • Multiple │
|
||||
│ • 100-200 words • 300-800 words • 800-2000 │
|
||||
│ • Basic structure • Full structure • Scripts │
|
||||
│ • No extras • Examples • Examples │
|
||||
│ • Best practices • Templates│
|
||||
│ • Docs │
|
||||
│ Example: Example: Example: │
|
||||
│ git-pushing brainstorming loki-mode │
|
||||
│ │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🎯 Contribution Impact (Visual)
|
||||
|
||||
```
|
||||
Your Contribution
|
||||
│
|
||||
├─→ Improves Documentation
|
||||
│ │
|
||||
│ └─→ Helps 1000s of developers understand
|
||||
│
|
||||
├─→ Creates New Skill
|
||||
│ │
|
||||
│ └─→ Enables new capabilities for everyone
|
||||
│
|
||||
├─→ Fixes Bug/Typo
|
||||
│ │
|
||||
│ └─→ Prevents confusion for future users
|
||||
│
|
||||
└─→ Adds Example
|
||||
│
|
||||
└─→ Makes learning easier for beginners
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Learning Path (Visual Roadmap)
|
||||
|
||||
```
|
||||
START HERE
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Read │
|
||||
│ GETTING_STARTED │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Try 2-3 Skills │
|
||||
│ in AI Assistant │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Read │
|
||||
│ SKILL_ANATOMY │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Study Existing │
|
||||
│ Skills │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Create Simple │
|
||||
│ Skill │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Read │
|
||||
│ CONTRIBUTING │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
┌─────────────────┐
|
||||
│ Submit PR │
|
||||
└────────┬────────┘
|
||||
│
|
||||
↓
|
||||
CONTRIBUTOR! 🎉
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 💡 Quick Tips (Visual Cheatsheet)
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ QUICK REFERENCE │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ │
|
||||
│ 📥 INSTALL │
|
||||
│ git clone [repo] .agent/skills │
|
||||
│ │
|
||||
│ 🎯 USE │
|
||||
│ @skill-name [your request] │
|
||||
│ │
|
||||
│ 🔍 FIND │
|
||||
│ ls skills/ | grep "keyword" │
|
||||
│ │
|
||||
│ ✅ VALIDATE │
|
||||
│ npm run validate │
|
||||
│ │
|
||||
│ 📝 CREATE │
|
||||
│ 1. mkdir skills/my-skill │
|
||||
│ 2. Create SKILL.md with frontmatter │
|
||||
│ 3. Add content │
|
||||
│ 4. Test & validate │
|
||||
│ 5. Submit PR │
|
||||
│ │
|
||||
│ 🆘 HELP │
|
||||
│ • docs/users/getting-started.md │
|
||||
│ • CONTRIBUTING.md │
|
||||
│ • docs/contributors/skill-anatomy.md │
|
||||
│ • GitHub Issues - Ask questions │
|
||||
│ │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Success Stories (Visual Timeline)
|
||||
|
||||
```
|
||||
Day 1: Install skills
|
||||
│
|
||||
└─→ "Wow, @brainstorming helped me design my app!"
|
||||
|
||||
Day 3: Use 5 different skills
|
||||
│
|
||||
└─→ "These skills save me so much time!"
|
||||
|
||||
Week 1: Create first skill
|
||||
│
|
||||
└─→ "I shared my expertise as a skill!"
|
||||
|
||||
Week 2: Skill gets merged
|
||||
│
|
||||
└─→ "My skill is helping others! 🎉"
|
||||
|
||||
Month 1: Regular contributor
|
||||
│
|
||||
└─→ "I've contributed 5 skills and improved docs!"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. ✅ **Understand** the visual structure
|
||||
2. ✅ **Install** skills in your AI tool
|
||||
3. ✅ **Try** 2-3 skills from different categories
|
||||
4. ✅ **Read** CONTRIBUTING.md
|
||||
5. ✅ **Create** your first skill
|
||||
6. ✅ **Share** with the community
|
||||
|
||||
---
|
||||
|
||||
**Visual learner?** This guide should help! Still have questions? Check out:
|
||||
- [getting-started.md](getting-started.md) - Text-based intro
|
||||
- [skill-anatomy.md](../contributors/skill-anatomy.md) - Detailed breakdown
|
||||
- [CONTRIBUTING.md](../../CONTRIBUTING.md) - How to contribute
|
||||
|
||||
**Ready to contribute?** You've got this! 💪
|
||||
215
docs/users/workflows.md
Normal file
215
docs/users/workflows.md
Normal file
@@ -0,0 +1,215 @@
|
||||
# Antigravity Workflows
|
||||
|
||||
> Workflow playbooks to orchestrate multiple skills with less friction.
|
||||
|
||||
## What Is a Workflow?
|
||||
|
||||
A workflow is a guided, step-by-step execution path that combines multiple skills for one concrete outcome.
|
||||
|
||||
- **Bundles** tell you which skills are relevant for a role.
|
||||
- **Workflows** tell you how to use those skills in sequence to complete a real objective.
|
||||
|
||||
If bundles are your toolbox, workflows are your execution playbook.
|
||||
|
||||
---
|
||||
|
||||
## How to Use Workflows
|
||||
|
||||
1. Install the repository once (`npx antigravity-awesome-skills`).
|
||||
2. Pick a workflow matching your immediate goal.
|
||||
3. Execute steps in order and invoke the listed skills in each step.
|
||||
4. Keep output artifacts at each step (plan, decisions, tests, validation evidence).
|
||||
|
||||
You can combine workflows with bundles from [bundles.md](bundles.md) when you need broader coverage.
|
||||
|
||||
---
|
||||
|
||||
## Workflow: Ship a SaaS MVP
|
||||
|
||||
Build and ship a minimal but production-minded SaaS product.
|
||||
|
||||
**Related bundles:** `Essentials`, `Full-Stack Developer`, `QA & Testing`, `DevOps & Cloud`
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Local repository and runtime configured.
|
||||
- Clear user problem and MVP scope.
|
||||
- Basic deployment target selected.
|
||||
|
||||
### Steps
|
||||
|
||||
1. **Plan the scope**
|
||||
- **Goal:** Define MVP boundaries and acceptance criteria.
|
||||
- **Skills:** [`@brainstorming`](../../skills/brainstorming/), [`@concise-planning`](../../skills/concise-planning/), [`@writing-plans`](../../skills/writing-plans/)
|
||||
- **Prompt example:** `Usa @concise-planning per definire milestones e criteri di accettazione del mio MVP SaaS.`
|
||||
|
||||
2. **Build backend and API**
|
||||
- **Goal:** Implement core entities, APIs, and auth baseline.
|
||||
- **Skills:** [`@backend-dev-guidelines`](../../skills/backend-dev-guidelines/), [`@api-patterns`](../../skills/api-patterns/), [`@database-design`](../../skills/database-design/)
|
||||
- **Prompt example:** `Usa @backend-dev-guidelines per creare API e servizi del dominio billing.`
|
||||
|
||||
3. **Build frontend**
|
||||
- **Goal:** Ship core user flow with clear UX states.
|
||||
- **Skills:** [`@frontend-developer`](../../skills/frontend-developer/), [`@react-patterns`](../../skills/react-patterns/), [`@frontend-design`](../../skills/frontend-design/)
|
||||
- **Prompt example:** `Usa @frontend-developer per implementare onboarding, empty state e dashboard iniziale.`
|
||||
|
||||
4. **Test and validate**
|
||||
- **Goal:** Cover critical user journeys before release.
|
||||
- **Skills:** [`@test-driven-development`](../../skills/test-driven-development/), [`@browser-automation`](../../skills/browser-automation/), `@go-playwright` (optional, Go stack)
|
||||
- **Prompt example:** `Usa @browser-automation per creare test E2E sui flussi signup e checkout.`
|
||||
- **Go note:** Se il progetto QA e tooling sono in Go, preferisci `@go-playwright`.
|
||||
|
||||
5. **Ship safely**
|
||||
- **Goal:** Release with observability and rollback plan.
|
||||
- **Skills:** [`@deployment-procedures`](../../skills/deployment-procedures/), [`@observability-engineer`](../../skills/observability-engineer/)
|
||||
- **Prompt example:** `Usa @deployment-procedures per una checklist di rilascio con rollback.`
|
||||
|
||||
---
|
||||
|
||||
## Workflow: Security Audit for a Web App
|
||||
|
||||
Run a focused security review from scope definition to remediation validation.
|
||||
|
||||
**Related bundles:** `Security Engineer`, `Security Developer`, `Observability & Monitoring`
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Explicit authorization for testing.
|
||||
- In-scope targets documented.
|
||||
- Logging and environment details available.
|
||||
|
||||
### Steps
|
||||
|
||||
1. **Define scope and threat model**
|
||||
- **Goal:** Identify assets, trust boundaries, and attack paths.
|
||||
- **Skills:** [`@ethical-hacking-methodology`](../../skills/ethical-hacking-methodology/), [`@threat-modeling-expert`](../../skills/threat-modeling-expert/), [`@attack-tree-construction`](../../skills/attack-tree-construction/)
|
||||
- **Prompt example:** `Usa @threat-modeling-expert per mappare asset critici e trust boundaries della mia web app.`
|
||||
|
||||
2. **Review auth and access control**
|
||||
- **Goal:** Detect account takeover and authorization flaws.
|
||||
- **Skills:** [`@broken-authentication`](../../skills/broken-authentication/), [`@auth-implementation-patterns`](../../skills/auth-implementation-patterns/), [`@idor-testing`](../../skills/idor-testing/)
|
||||
- **Prompt example:** `Usa @idor-testing per verificare accessi non autorizzati su endpoint multitenant.`
|
||||
|
||||
3. **Assess API and input security**
|
||||
- **Goal:** Uncover high-impact API and injection vulnerabilities.
|
||||
- **Skills:** [`@api-security-best-practices`](../../skills/api-security-best-practices/), [`@api-fuzzing-bug-bounty`](../../skills/api-fuzzing-bug-bounty/), [`@top-web-vulnerabilities`](../../skills/top-web-vulnerabilities/)
|
||||
- **Prompt example:** `Usa @api-security-best-practices per audit endpoint auth, billing e admin.`
|
||||
|
||||
4. **Harden and verify**
|
||||
- **Goal:** Convert findings into fixes and verify evidence of mitigation.
|
||||
- **Skills:** [`@security-auditor`](../../skills/security-auditor/), [`@sast-configuration`](../../skills/sast-configuration/), [`@verification-before-completion`](../../skills/verification-before-completion/)
|
||||
- **Prompt example:** `Usa @verification-before-completion per provare che le mitigazioni sono effettive.`
|
||||
|
||||
---
|
||||
|
||||
## Workflow: Build an AI Agent System
|
||||
|
||||
Design and deliver a production-grade agent with measurable reliability.
|
||||
|
||||
**Related bundles:** `Agent Architect`, `LLM Application Developer`, `Data Engineering`
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Narrow use case with measurable outcomes.
|
||||
- Access to model provider(s) and observability tooling.
|
||||
- Initial dataset or knowledge corpus.
|
||||
|
||||
### Steps
|
||||
|
||||
1. **Define target behavior and KPIs**
|
||||
- **Goal:** Set quality, latency, and failure thresholds.
|
||||
- **Skills:** [`@ai-agents-architect`](../../skills/ai-agents-architect/), [`@agent-evaluation`](../../skills/agent-evaluation/), [`@product-manager-toolkit`](../../skills/product-manager-toolkit/)
|
||||
- **Prompt example:** `Usa @agent-evaluation per definire benchmark e criteri di successo del mio agente.`
|
||||
|
||||
2. **Design retrieval and memory**
|
||||
- **Goal:** Build reliable retrieval and context architecture.
|
||||
- **Skills:** [`@llm-app-patterns`](../../skills/llm-app-patterns/), [`@rag-implementation`](../../skills/rag-implementation/), [`@vector-database-engineer`](../../skills/vector-database-engineer/)
|
||||
- **Prompt example:** `Usa @rag-implementation per progettare pipeline di chunking, embedding e retrieval.`
|
||||
|
||||
3. **Implement orchestration**
|
||||
- **Goal:** Implement deterministic orchestration and tool boundaries.
|
||||
- **Skills:** [`@langgraph`](../../skills/langgraph/), [`@mcp-builder`](../../skills/mcp-builder/), [`@workflow-automation`](../../skills/workflow-automation/)
|
||||
- **Prompt example:** `Usa @langgraph per implementare il grafo agente con fallback e human-in-the-loop.`
|
||||
|
||||
4. **Evaluate and iterate**
|
||||
- **Goal:** Improve weak points with a structured loop.
|
||||
- **Skills:** [`@agent-evaluation`](../../skills/agent-evaluation/), [`@langfuse`](../../skills/langfuse/), [`@kaizen`](../../skills/kaizen/)
|
||||
- **Prompt example:** `Usa @kaizen per prioritizzare le correzioni sulle failure modes rilevate dai test.`
|
||||
|
||||
---
|
||||
|
||||
## Workflow: QA and Browser Automation
|
||||
|
||||
Create resilient browser automation with deterministic execution in CI.
|
||||
|
||||
**Related bundles:** `QA & Testing`, `Full-Stack Developer`
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Test environments and stable credentials.
|
||||
- Critical user journeys identified.
|
||||
- CI pipeline available.
|
||||
|
||||
### Steps
|
||||
|
||||
1. **Prepare test strategy**
|
||||
- **Goal:** Scope journeys, fixtures, and execution environments.
|
||||
- **Skills:** [`@e2e-testing-patterns`](../../skills/e2e-testing-patterns/), [`@test-driven-development`](../../skills/test-driven-development/)
|
||||
- **Prompt example:** `Usa @e2e-testing-patterns per definire suite E2E minima ma ad alto impatto.`
|
||||
|
||||
2. **Implement browser tests**
|
||||
- **Goal:** Build robust test coverage with stable selectors.
|
||||
- **Skills:** [`@browser-automation`](../../skills/browser-automation/), `@go-playwright` (optional, Go stack)
|
||||
- **Prompt example:** `Usa @go-playwright per implementare browser automation in un progetto Go.`
|
||||
|
||||
3. **Triage and harden**
|
||||
- **Goal:** Remove flaky behavior and enforce repeatability.
|
||||
- **Skills:** [`@systematic-debugging`](../../skills/systematic-debugging/), [`@test-fixing`](../../skills/test-fixing/), [`@verification-before-completion`](../../skills/verification-before-completion/)
|
||||
- **Prompt example:** `Usa @systematic-debugging per classificare e risolvere le flakiness in CI.`
|
||||
|
||||
---
|
||||
|
||||
## Workflow: Design a DDD Core Domain
|
||||
|
||||
Model a complex domain coherently, then implement tactical and evented patterns only where justified.
|
||||
|
||||
**Related bundles:** `Architecture & Design`, `DDD & Evented Architecture`
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Access to at least one domain expert or product owner proxy.
|
||||
- Current system context and integration landscape available.
|
||||
- Agreement on business goals and key domain outcomes.
|
||||
|
||||
### Steps
|
||||
|
||||
1. **Assess DDD fit and scope**
|
||||
- **Goal:** Decide whether full DDD, partial DDD, or simple modular architecture is appropriate.
|
||||
- **Skills:** [`@domain-driven-design`](../../skills/domain-driven-design/), [`@architecture-decision-records`](../../skills/architecture-decision-records/)
|
||||
- **Prompt example:** `Use @domain-driven-design to evaluate if full DDD is justified for our billing and fulfillment platform.`
|
||||
|
||||
2. **Create strategic model**
|
||||
- **Goal:** Define subdomains, bounded contexts, and ubiquitous language.
|
||||
- **Skills:** [`@ddd-strategic-design`](../../skills/ddd-strategic-design/)
|
||||
- **Prompt example:** `Use @ddd-strategic-design to classify subdomains and propose bounded contexts with ownership.`
|
||||
|
||||
3. **Map context relationships**
|
||||
- **Goal:** Define upstream/downstream contracts and anti-corruption boundaries.
|
||||
- **Skills:** [`@ddd-context-mapping`](../../skills/ddd-context-mapping/)
|
||||
- **Prompt example:** `Use @ddd-context-mapping to model Checkout, Billing, and Inventory interactions with clear contract ownership.`
|
||||
|
||||
4. **Implement tactical model**
|
||||
- **Goal:** Encode invariants with aggregates, value objects, and domain events.
|
||||
- **Skills:** [`@ddd-tactical-patterns`](../../skills/ddd-tactical-patterns/), [`@test-driven-development`](../../skills/test-driven-development/)
|
||||
- **Prompt example:** `Use @ddd-tactical-patterns to design aggregates and invariants for order lifecycle transitions.`
|
||||
|
||||
5. **Adopt evented patterns selectively**
|
||||
- **Goal:** Apply CQRS, event store, projections, and sagas only where complexity and scale require them.
|
||||
- **Skills:** [`@cqrs-implementation`](../../skills/cqrs-implementation/), [`@event-store-design`](../../skills/event-store-design/), [`@projection-patterns`](../../skills/projection-patterns/), [`@saga-orchestration`](../../skills/saga-orchestration/)
|
||||
- **Prompt example:** `Use @cqrs-implementation and @projection-patterns to scale read-side reporting without compromising domain invariants.`
|
||||
|
||||
---
|
||||
|
||||
## Machine-Readable Workflows
|
||||
|
||||
For tooling and automation, workflow metadata is available in [data/workflows.json](../../data/workflows.json).
|
||||
Reference in New Issue
Block a user