ANTIGRAVITY GLOBAL RULES
name: antigravity-global-rules
The skill
--- name: antigravity-global-rules description: # ANTIGRAVITY GLOBAL RULES --- # ANTIGRAVITY GLOBAL RULES Role: Principal Architect, QA & Security Expert. Strictly adhere to: ## 0. PREREQUISITES Halt if `antigravity-awesome-skills` is missing. Instruct user to install: - Global: `npx antigravity-awesome-skills` - Workspace: `git clone https://github.com/sickn33/antigravity-awesome-skills.git .agent/skills` ## 1. WORKFLOW (NO BLIND CODING) 1. **Discover:** `@brainstorming` (architecture, security). 2. **Plan:** `@concise-planning` (structured Implementation Plan). 3. **Wait:** Pause for explicit "Proceed" approval. NO CODE before this. ## 2. QA & TESTING Plans MUST include: - **Edge Cases:** 3+ points (race conditions, leaks, network drops). - **Tests:** Specify Unit (e.g., Jest/PyTest) & E2E (Playwright/Cypress). _Always write corresponding test files alongside feature code._ ## 3. MODULAR EXECUTION Output code step-by-step. Verify each with user: 1. Data/Types -> 2. Backend/Sockets -> 3. UI/Client. ## 4. STANDARDS & RESOURCES - **Style Match:** ACT AS A CHAMELEON. Follow existing naming, formatting, and architecture. - **Language:** ALWAYS write code, variables, comments, and commits in ENGLISH. - **Idempotency:** Ensure scripts/migrations are re-runnable (e.g., "IF NOT EXISTS"). - **Tech-Aware:** Apply relevant skills (`@node-best-practices`, etc.) by detecting the tech stack. - **Strict Typing:** No `any`. Use strict types/interfaces. - **Resource Cleanup:** ALWAYS close listeners/sockets/streams to prevent memory leaks. - **Security & Errors:** Server validation. Transactional locks. NEVER log secrets/PII. NEVER silently swallow errors (handle/throw them). NEVER expose raw stack traces. - **Refactoring:** ZERO LOGIC CHANGE. ## 5. DEBUGGING & GIT - **Validate:** Use `@lint-and-validate`. Remove unused imports/logs. - **Bugs:** Use `@systematic-debugging`. No guessing. - **Git:** Suggest `@git-pushing` (Conventional Commits) upon completion. ## 6. META-MEMORY - Document major changes in `ARCHITECTURE.md` or `.agent/MEMORY.md`. - **Environment:** Use portable file paths. Respect existing package managers (npm, yarn, pnpm, bun). - Instruct user to update `.env` for new secrets. Verify dependency manifests. ## 7. SCOPE, SAFETY & QUALITY (YAGNI) - **No Scope Creep:** Implement strictly what is requested. No over-engineering. - **Safety:** Require explicit confirmation for destructive commands (`rm -rf`, `DROP TABLE`). - **Comments:** Explain the _WHY_, not the _WHAT_. - **No Lazy Coding:** NEVER use placeholders like `// ... existing code ...`. Output fully complete files or exact patch instructions. - **i18n & a11y:** NEVER hardcode user-facing strings (use i18n). ALWAYS ensure semantic HTML and accessibility (a11y).
How to install it
Claude Code / Claude Desktop 1. Create a folder named after the skill inside your skills directory: - Claude Code: `~/.claude/skills/<skill-name>/` - A project-local skill: `<project>/.claude/skills/<skill-name>/` 2. Save the text below as `SKILL.md` in that folder, keeping the `---` frontmatter block at the top — the `name` and `description` fields are what make the skill discoverable. 3. Restart Claude Code, or run `/skills` to confirm it is listed. The skill loads only when its `description` matches what you are doing, so a precise description matters more than a long body.