ok
This commit is contained in:
@@ -5,6 +5,7 @@
|
||||
## 🚀 Quick Start
|
||||
|
||||
1. **Install the repository:**
|
||||
|
||||
```bash
|
||||
npx antigravity-awesome-skills
|
||||
# or clone manually
|
||||
@@ -421,21 +422,25 @@ Keep a small list of high-frequency skills and reuse it across tasks to reduce c
|
||||
### 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
|
||||
@@ -456,4 +461,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
|
||||
|
||||
---
|
||||
|
||||
_Last updated: February 2026 | Total Skills: 713+ | Total Bundles: 26_
|
||||
_Last updated: February 2026 | Total Skills: 954+ | Total Bundles: 26_
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# Getting Started with Antigravity Awesome Skills (V4)
|
||||
# Getting Started with Antigravity Awesome Skills (V6.5.0)
|
||||
|
||||
**New here? This guide will help you supercharge your AI Agent in 5 minutes.**
|
||||
|
||||
@@ -17,7 +17,7 @@ AI Agents (like **Claude Code**, **Gemini**, **Cursor**) are smart, but they lac
|
||||
|
||||
## ⚡️ Quick Start: The "Starter Packs"
|
||||
|
||||
Don't panic about the 700+ skills. You don't need them all at once.
|
||||
Don't panic about the 954+ 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.
|
||||
@@ -30,7 +30,7 @@ You **install the full repo once** (npx or clone); Starter Packs are curated lis
|
||||
npx antigravity-awesome-skills
|
||||
```
|
||||
|
||||
This clones to `~/.agent/skills` by default. Use `--cursor`, `--claude`, `--gemini`, or `--codex` to install for a specific tool, or `--path <dir>` for a custom location. Run `npx antigravity-awesome-skills --help` for details.
|
||||
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`
|
||||
|
||||
@@ -95,14 +95,18 @@ Once installed, just talk to your AI naturally.
|
||||
|
||||
## 🔌 Supported Tools
|
||||
|
||||
| Tool | Status | Path |
|
||||
| :-------------- | :-------------- | :---------------- |
|
||||
| **Claude Code** | ✅ Full Support | `.claude/skills/` |
|
||||
| **Gemini CLI** | ✅ Full Support | `.gemini/skills/` |
|
||||
| **Codex CLI** | ✅ Full Support | `.codex/skills/` |
|
||||
| **Antigravity** | ✅ Native | `.agent/skills/` |
|
||||
| **Cursor** | ✅ Native | `.cursor/skills/` |
|
||||
| **Copilot** | ⚠️ Text Only | Manual copy-paste |
|
||||
| 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 |
|
||||
|
||||
---
|
||||
|
||||
@@ -120,7 +124,7 @@ _Check the [Skill Catalog](../CATALOG.md) for the full list._
|
||||
|
||||
## ❓ FAQ
|
||||
|
||||
**Q: Do I need to install all 700+ skills?**
|
||||
**Q: Do I need to install all 954+ 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?**
|
||||
|
||||
@@ -7,6 +7,7 @@ This guide explains how to use Antigravity Awesome Skills with **Kiro CLI**, AWS
|
||||
## 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
|
||||
@@ -16,7 +17,8 @@ Kiro is AWS's agentic AI IDE that combines:
|
||||
## Why Use Skills with Kiro?
|
||||
|
||||
Kiro's agentic capabilities are enhanced by skills that provide:
|
||||
- **Domain expertise** across 883+ specialized areas
|
||||
|
||||
- **Domain expertise** across 954+ 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
|
||||
@@ -68,6 +70,7 @@ 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
|
||||
@@ -76,24 +79,28 @@ Run @security-audit on my CDK stack
|
||||
- `@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
|
||||
@@ -134,12 +141,14 @@ Run @security-audit on my CDK stack
|
||||
### 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
|
||||
@@ -149,8 +158,8 @@ Skills that leverage MCP:
|
||||
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
|
||||
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.
|
||||
```
|
||||
|
||||
@@ -159,8 +168,8 @@ to update all README files.
|
||||
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,
|
||||
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.
|
||||
```
|
||||
|
||||
@@ -169,6 +178,7 @@ I'm building a SaaS application. Use @brainstorming for the MVP plan,
|
||||
Pre-curated skill collections optimized for common Kiro use cases:
|
||||
|
||||
### AWS Developer Bundle
|
||||
|
||||
- `@aws-serverless`
|
||||
- `@aws-cdk`
|
||||
- `@aws-sam`
|
||||
@@ -177,6 +187,7 @@ Pre-curated skill collections optimized for common Kiro use cases:
|
||||
- `@api-gateway-patterns`
|
||||
|
||||
### Full-Stack AWS Bundle
|
||||
|
||||
- `@aws-serverless`
|
||||
- `@react-patterns`
|
||||
- `@typescript-expert`
|
||||
@@ -185,6 +196,7 @@ Pre-curated skill collections optimized for common Kiro use cases:
|
||||
- `@ci-cd-pipeline`
|
||||
|
||||
### DevOps & Infrastructure Bundle
|
||||
|
||||
- `@terraform-expert`
|
||||
- `@docker-expert`
|
||||
- `@kubernetes-expert`
|
||||
@@ -238,8 +250,8 @@ chmod -R 755 ~/.kiro/skills/
|
||||
```
|
||||
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,
|
||||
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.
|
||||
@@ -250,8 +262,8 @@ Generate the infrastructure using @aws-cdk and add tests with @test-driven-devel
|
||||
```
|
||||
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,
|
||||
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.
|
||||
@@ -262,8 +274,8 @@ Document the migration plan with @documentation.
|
||||
```
|
||||
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,
|
||||
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.
|
||||
|
||||
@@ -3,16 +3,16 @@
|
||||
We believe in giving credit where credit is due.
|
||||
If you recognize your work here and it is not properly attributed, please open an Issue.
|
||||
|
||||
| Skill / Category | Original Source | License | Notes |
|
||||
| :-------------------------- | :----------------------------------------------------------------- | :------------- | :---------------------------- |
|
||||
| `cloud-penetration-testing` | [HackTricks](https://book.hacktricks.xyz/) | MIT / CC-BY-SA | Adapted for agentic use. |
|
||||
| `active-directory-attacks` | [HackTricks](https://book.hacktricks.xyz/) | MIT / CC-BY-SA | Adapted for agentic use. |
|
||||
| `owasp-top-10` | [OWASP](https://owasp.org/) | CC-BY-SA | Methodology adapted. |
|
||||
| `burp-suite-testing` | [PortSwigger](https://portswigger.net/burp) | N/A | Usage guide only (no binary). |
|
||||
| `crewai` | [CrewAI](https://github.com/joaomdmoura/crewAI) | MIT | Framework guides. |
|
||||
| `langgraph` | [LangGraph](https://github.com/langchain-ai/langgraph) | MIT | Framework guides. |
|
||||
| `react-patterns` | [React Docs](https://react.dev/) | CC-BY | Official patterns. |
|
||||
| **All Official Skills** | [Anthropic / Google / OpenAI / Microsoft / Supabase / Vercel Labs] | Proprietary | Usage encouraged by vendors. |
|
||||
| Skill / Category | Original Source | License | Notes |
|
||||
| :-------------------------- | :------------------------------------------------------------------------- | :------------- | :---------------------------- |
|
||||
| `cloud-penetration-testing` | [HackTricks](https://book.hacktricks.xyz/) | MIT / CC-BY-SA | Adapted for agentic use. |
|
||||
| `active-directory-attacks` | [HackTricks](https://book.hacktricks.xyz/) | MIT / CC-BY-SA | Adapted for agentic use. |
|
||||
| `owasp-top-10` | [OWASP](https://owasp.org/) | CC-BY-SA | Methodology adapted. |
|
||||
| `burp-suite-testing` | [PortSwigger](https://portswigger.net/burp) | N/A | Usage guide only (no binary). |
|
||||
| `crewai` | [CrewAI](https://github.com/joaomdmoura/crewAI) | MIT | Framework guides. |
|
||||
| `langgraph` | [LangGraph](https://github.com/langchain-ai/langgraph) | MIT | Framework guides. |
|
||||
| `react-patterns` | [React Docs](https://react.dev/) | CC-BY | Official patterns. |
|
||||
| **All Official Skills** | [Anthropic / Google / OpenAI / Microsoft / Supabase / Apify / Vercel Labs] | Proprietary | Usage encouraged by vendors. |
|
||||
|
||||
## Skills from VoltAgent/awesome-agent-skills
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Great question! Here's what just happened and what to do next:
|
||||
|
||||
When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
|
||||
|
||||
✅ **Downloaded 883+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or `~/.agent/skills/` if you used `--path`)
|
||||
✅ **Downloaded 954+ 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)
|
||||
|
||||
@@ -30,8 +30,9 @@ Think of it like installing a toolbox. You have all the tools now, but you need
|
||||
|
||||
Bundles are **recommended lists** of skills grouped by role. They help you decide which skills to start using.
|
||||
|
||||
**Analogy:**
|
||||
- You installed a toolbox with 883+ tools (✅ done)
|
||||
**Analogy:**
|
||||
|
||||
- You installed a toolbox with 954+ 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**
|
||||
|
||||
@@ -44,6 +45,7 @@ Bundles are **recommended lists** of skills grouped by role. They help you decid
|
||||
### 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`
|
||||
@@ -66,30 +68,35 @@ This is the part that should have been explained better! Here's how to use skill
|
||||
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
|
||||
@@ -105,10 +112,12 @@ Here are **real-world examples** of good prompts:
|
||||
|
||||
### Example 1: Starting a New Project
|
||||
|
||||
**Bad Prompt:**
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Help me build a todo app"
|
||||
|
||||
**Good Prompt:**
|
||||
**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.
|
||||
@@ -117,10 +126,12 @@ Here are **real-world examples** of good prompts:
|
||||
|
||||
### Example 2: Reviewing Code
|
||||
|
||||
**Bad Prompt:**
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Check my code"
|
||||
|
||||
**Good Prompt:**
|
||||
**Good Prompt:**
|
||||
|
||||
> "Use @lint-and-validate to check `src/components/Button.tsx` for issues"
|
||||
|
||||
**Why it's better:** Specific skill + specific file = precise results.
|
||||
@@ -129,10 +140,12 @@ Here are **real-world examples** of good prompts:
|
||||
|
||||
### Example 3: Security Audit
|
||||
|
||||
**Bad Prompt:**
|
||||
**Bad Prompt:**
|
||||
|
||||
> "Make my API secure"
|
||||
|
||||
**Good Prompt:**
|
||||
**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.
|
||||
@@ -141,7 +154,8 @@ Here are **real-world examples** of good prompts:
|
||||
|
||||
### Example 4: Combining Multiple Skills
|
||||
|
||||
**Good Prompt:**
|
||||
**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!
|
||||
@@ -159,6 +173,7 @@ Let's actually use a skill right now. Follow these steps:
|
||||
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
|
||||
```
|
||||
@@ -177,17 +192,18 @@ Let's actually use a skill right now. Follow these steps:
|
||||
|
||||
## 🗂️ Step 5: Picking Your First Skills (Practical Advice)
|
||||
|
||||
Don't try to use all 883+ skills! Here's a sensible approach:
|
||||
Don't try to use all 954+ skills! 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
|
||||
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`
|
||||
@@ -198,12 +214,14 @@ Don't try to use all 883+ skills! Here's a sensible approach:
|
||||
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`
|
||||
@@ -224,6 +242,7 @@ 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
|
||||
|
||||
@@ -233,6 +252,7 @@ AI: [Produces detailed design spec]
|
||||
```
|
||||
|
||||
#### Step 2: Implement (use @nextjs-best-practices)
|
||||
|
||||
```
|
||||
You: Use @nextjs-best-practices to scaffold the blog with App Router
|
||||
|
||||
@@ -240,6 +260,7 @@ 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
|
||||
|
||||
@@ -247,6 +268,7 @@ AI: [Applies Tailwind styling with responsive design]
|
||||
```
|
||||
|
||||
#### Step 4: SEO (use @seo-audit)
|
||||
|
||||
```
|
||||
You: Use @seo-audit to optimize the blog for search engines
|
||||
|
||||
@@ -254,6 +276,7 @@ AI: [Adds meta tags, sitemaps, structured data]
|
||||
```
|
||||
|
||||
#### Step 5: Test & Deploy
|
||||
|
||||
```
|
||||
You: Use @test-driven-development to add tests, then @vercel-deployment to deploy
|
||||
|
||||
@@ -269,6 +292,7 @@ AI: [Creates tests, sets up CI/CD, deploys to Vercel]
|
||||
### "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
|
||||
@@ -277,6 +301,7 @@ AI: [Creates tests, sets up CI/CD, deploys to Vercel]
|
||||
### "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]?"
|
||||
@@ -284,6 +309,7 @@ Yes! Three ways:
|
||||
### "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.)
|
||||
@@ -291,6 +317,7 @@ Usually no, but if your AI doesn't recognize a skill:
|
||||
### "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]
|
||||
```
|
||||
@@ -307,15 +334,15 @@ Use @skill-creator to help me build a custom skill for [your task]
|
||||
|
||||
**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` |
|
||||
| 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` |
|
||||
|
||||
---
|
||||
|
||||
@@ -333,19 +360,24 @@ Now that you understand how to use skills:
|
||||
## 💡 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"
|
||||
|
||||
---
|
||||
|
||||
@@ -30,7 +30,7 @@
|
||||
Các trợ lý AI (như Claude Code, Cursor, hoặc Gemini) rất thông minh, nhưng chúng thiếu các **công cụ chuyên biệt**. Chúng không biết "Quy trình Triển khai" của công ty bạn hoặc cú pháp cụ thể cho "AWS CloudFormation".
|
||||
**Skills** là các tệp markdown nhỏ dạy cho chúng cách thực hiện những tác vụ cụ thể này một cách chính xác trong mọi lần thực thi.
|
||||
...
|
||||
Repository này cung cấp các kỹ năng thiết yếu để biến trợ lý AI của bạn thành một **đội ngũ chuyên gia số toàn năng**, bao gồm các khả năng chính thức từ **Anthropic**, **OpenAI**, **Google**, **Supabase**, và **Vercel Labs**.
|
||||
Repository này cung cấp các kỹ năng thiết yếu để biến trợ lý AI của bạn thành một **đội ngũ chuyên gia số toàn năng**, bao gồm các khả năng chính thức từ **Anthropic**, **OpenAI**, **Google**, **Supabase**, **Apify**, và **Vercel Labs**.
|
||||
...
|
||||
Cho dù bạn đang sử dụng **Gemini CLI**, **Claude Code**, **Codex CLI**, **Cursor**, **GitHub Copilot**, **Antigravity**, hay **OpenCode**, những kỹ năng này được thiết kế để có thể sử dụng ngay lập tức và tăng cường sức mạnh cho trợ lý AI của bạn.
|
||||
|
||||
@@ -40,17 +40,17 @@ Repository này tập hợp những khả năng tốt nhất từ khắp cộng
|
||||
|
||||
Repository được tổ chức thành các lĩnh vực chuyên biệt để biến AI của bạn thành một chuyên gia trên toàn bộ vòng đời phát triển phần mềm:
|
||||
|
||||
| Danh mục | Trọng tâm | Ví dụ kỹ năng |
|
||||
| :--- | :--- | :--- |
|
||||
| Kiến trúc (52) | Thiết kế hệ thống, ADRs, C4 và các mẫu có thể mở rộng | `architecture`, `c4-context`, `senior-architect` |
|
||||
| Kinh doanh (35) | Tăng trưởng, định giá, CRO, SEO và thâm nhập thị trường | `copywriting`, `pricing-strategy`, `seo-audit` |
|
||||
| Dữ liệu & AI (81) | Ứng dụng LLM, RAG, agents, khả năng quan sát, phân tích | `rag-engineer`, `prompt-engineer`, `langgraph` |
|
||||
| Phát triển (72) | Làm chủ ngôn ngữ, mẫu thiết kế framework, chất lượng code | `typescript-expert`, `python-patterns`, `react-patterns` |
|
||||
| Tổng quát (95) | Lập kế hoạch, tài liệu, vận hành sản phẩm, viết bài, hướng dẫn | `brainstorming`, `doc-coauthoring`, `writing-plans` |
|
||||
| Hạ tầng (72) | DevOps, cloud, serverless, triển khai, CI/CD | `docker-expert`, `aws-serverless`, `vercel-deployment` |
|
||||
| Bảo mật (107) | AppSec, pentesting, phân tích lỗ hổng, tuân thủ | `api-security-best-practices`, `sql-injection-testing`, `vulnerability-scanner` |
|
||||
| Kiểm thử (21) | TDD, thiết kế kiểm thử, sửa lỗi, quy trình QA | `test-driven-development`, `testing-patterns`, `test-fixing` |
|
||||
| Quy trình (17) | Tự động hóa, điều phối, công việc, agents | `workflow-automation`, `inngest`, `trigger-dev` |
|
||||
| Danh mục | Trọng tâm | Ví dụ kỹ năng |
|
||||
| :---------------- | :------------------------------------------------------------- | :------------------------------------------------------------------------------ |
|
||||
| Kiến trúc (52) | Thiết kế hệ thống, ADRs, C4 và các mẫu có thể mở rộng | `architecture`, `c4-context`, `senior-architect` |
|
||||
| Kinh doanh (35) | Tăng trưởng, định giá, CRO, SEO và thâm nhập thị trường | `copywriting`, `pricing-strategy`, `seo-audit` |
|
||||
| Dữ liệu & AI (81) | Ứng dụng LLM, RAG, agents, khả năng quan sát, phân tích | `rag-engineer`, `prompt-engineer`, `langgraph` |
|
||||
| Phát triển (72) | Làm chủ ngôn ngữ, mẫu thiết kế framework, chất lượng code | `typescript-expert`, `python-patterns`, `react-patterns` |
|
||||
| Tổng quát (95) | Lập kế hoạch, tài liệu, vận hành sản phẩm, viết bài, hướng dẫn | `brainstorming`, `doc-coauthoring`, `writing-plans` |
|
||||
| Hạ tầng (72) | DevOps, cloud, serverless, triển khai, CI/CD | `docker-expert`, `aws-serverless`, `vercel-deployment` |
|
||||
| Bảo mật (107) | AppSec, pentesting, phân tích lỗ hổng, tuân thủ | `api-security-best-practices`, `sql-injection-testing`, `vulnerability-scanner` |
|
||||
| Kiểm thử (21) | TDD, thiết kế kiểm thử, sửa lỗi, quy trình QA | `test-driven-development`, `testing-patterns`, `test-fixing` |
|
||||
| Quy trình (17) | Tự động hóa, điều phối, công việc, agents | `workflow-automation`, `inngest`, `trigger-dev` |
|
||||
|
||||
## Bộ sưu tập Tuyển chọn
|
||||
|
||||
@@ -119,6 +119,7 @@ Bộ sưu tập này sẽ không thể hình thành nếu không có công việ
|
||||
- **[vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills)**: Skills chính thức của Vercel Labs - Thực hành tốt nhất cho React, Hướng dẫn thiết kế Web.
|
||||
- **[openai/skills](https://github.com/openai/skills)**: Danh mục skill của OpenAI Codex - Các kỹ năng của Agent, Trình tạo Skill, Lập kế hoạch Súc tích.
|
||||
- **[supabase/agent-skills](https://github.com/supabase/agent-skills)**: Skills chính thức của Supabase - Thực hành tốt nhất cho Postgres.
|
||||
- **[apify/agent-skills](https://github.com/apify/agent-skills)**: Skills chính thức của Apify - Web scraping, data extraction and automation.
|
||||
|
||||
### Những người đóng góp từ Cộng đồng
|
||||
|
||||
|
||||
Reference in New Issue
Block a user