agy-superpowers 5.1.8 → 5.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agy-superpowers",
-  "version": "5.1.8",
+  "version": "5.2.0",
   "description": "Superpowers skills library for Google Antigravity agent — scaffold .agent/ with one command",
   "type": "module",
   "bin": {

package/template/agent/rules/code-styles.md

@@ -0,0 +1,69 @@
+---
+description: Enforce project code styles — agent MUST read and follow these rules before writing any code
+alwaysApply: true
+---
+
+# Code Styles
+
+<HARD-GATE>
+Before writing, modifying, or generating ANY code, you MUST read this file and strictly follow every rule defined below.
+If a section is empty, skip it — but never skip reading this file.
+</HARD-GATE>
+
+## How to Use
+
+Fill in the sections below with your project's code style rules.
+Delete the placeholder comments and replace them with your actual conventions.
+
+---
+
+## Naming Conventions
+
+<!-- Examples:
+- Variables: camelCase
+- Components: PascalCase
+- Files: kebab-case
+- Constants: UPPER_SNAKE_CASE
+-->
+
+## File & Folder Structure
+
+<!-- Examples:
+- Feature-based folder structure
+- One component per file
+- Index files for barrel exports
+-->
+
+## Formatting
+
+<!-- Examples:
+- Indentation: 2 spaces
+- Max line length: 100
+- Semicolons: always / never
+- Quotes: single / double
+-->
+
+## Comments & Documentation
+
+<!-- Examples:
+- JSDoc for public functions
+- No obvious comments
+- TODO format: // TODO(username): description
+-->
+
+## Patterns & Conventions
+
+<!-- Examples:
+- State management: Zustand
+- Error handling: try/catch with custom error classes
+- Async: async/await over .then()
+- Imports order: external → internal → types
+-->
+
+## Anti-Patterns (DO NOT)
+
+<!-- Examples:
+- No any type in TypeScript
+- No console.log in production code
+- No inline styles in React components
+-->

package/template/agent/rules/file-length-policy.md

@@ -0,0 +1,64 @@
+---
+description: File length policy — apply when creating or editing files in .agent/rules/
+alwaysApply: true
+priority: critical
+---
+
+> **⚠️ CRITICAL PRIORITY — This rule overrides all other instructions about file editing.**
+> Check file length BEFORE writing. No exceptions.
+
+<HARD-GATE>
+Do NOT write, append, or edit any file in `.agent/rules/` until you have checked its current character count.
+If adding content would push the file past 12,000 characters, you MUST create a new file instead.
+This gate applies exclusively to `.agent/rules/` files.
+</HARD-GATE>
+
+# File Length Policy
+
+## Hard Limit: 12,000 Characters Per File
+
+Every file in `.agent/rules/` has a **hard character limit of 12,000 characters**.
+
+Before writing or appending to any `.agent/rules/` file, check the current file size:
+- If the current content **plus** the new content will exceed 12,000 characters → **do NOT add to the existing file**
+- Instead → **create a new file** following the naming convention below
+
+## When Content Overflows: Create a New File
+
+### Naming Convention
+
+Split content into numbered parts:
+
+```
+original-file.md         ← Part 1 (keep as-is, trim if needed)
+original-file-part2.md   ← Part 2 (new file for overflow)
+original-file-part3.md   ← Part 3 (continue if needed)
+```
+
+### Cross-Reference Between Parts
+
+At the **bottom** of the original file, add:
+```
+## See Also
+- [Continued in original-file-part2.md](./original-file-part2.md)
+```
+
+At the **top** of the new file, add:
+```
+<!-- Part 2 of original-file.md -->
+```
+
+## Why This Matters
+
+LLM context windows process rules most reliably when individual files stay concise. Files over 12,000 characters risk:
+- Partial truncation during loading
+- Reduced rule adherence near the end of the file
+- Harder human maintenance
+
+## Examples
+
+| Situation | Action |
+|---|---|
+| Adding 500 chars to a 11,800-char file | Create `filename-part2.md` for the new content |
+| Adding 200 chars to a 5,000-char file | Safe — append directly |
+| Refactoring a 15,000-char existing file | Split into two files immediately |