ac-framework 2.3.0 → 2.4.0

package/framework/web_development/CLAUDE.md

@@ -15,6 +15,7 @@ If you attempt to proceed without completing a required step, you MUST STOP and
 | Skill | Description | Primary Use | Required Before |
 |-------|-------------|-------------|-----------------|
 | `secure-coding-cybersecurity` | Detects and prevents security vulnerabilities (SQLi, XSS, command injection, hardcoded secrets). Follows OWASP Top 10 standards. | Secure code validation | `code-maintainability` |
+| `vibe-security` | Final security audit focused on AI-generated/vibe-coded risks (exposed keys, broken access control, auth/payment/data validation gaps). | Final security validation before closure | `openspec-archive-change` |
 | `code-maintainability` | Analyzes code maintainability: duplication, documentation, error handling, naming conventions, SOLID architecture, performance. | Refactoring and standards | `project-constitution` |
 | `error-handling-patterns` | Error handling patterns in multiple languages: exceptions, Result types, retry, circuit breaker, graceful degradation. | Application resilience | `secure-coding-cybersecurity` |
 | `performance-optimizer` | Methodologies for measuring, profiling, and optimizing code (caching, algorithm complexity, resource usage). | Performance Engineering | After Implementation |
@@ -99,6 +100,80 @@ acfm memory stats
 **User communication:** "Memory saved: [brief description]" when auto-saving occurs.
 
 
+
+### SynapseGrid Collaborative MCP Protocol (Optional)
+
+If SynapseGrid is enabled in `acfm init`, AC Framework installs the collaborative MCP server automatically for detected assistants.
+
+**When to delegate to SynapseGrid:**
+- Multi-step features with architecture + implementation + review work
+- Tasks requiring critical analysis before coding (security, API contracts, refactors)
+- Long-running work where transcript, artifacts, and resumability are important
+- Situations where one assistant would benefit from role-based challenge/review
+
+**Role delegation model (what each agent does best):**
+- `planner`: breaks down scope, constraints, approach, acceptance criteria
+- `critic`: challenges assumptions, finds risks/blind spots, proposes safer alternatives
+- `coder`: implements code and applies concrete changes
+- `reviewer`: validates quality, consistency with spec/tasks, and production readiness
+
+**Session-start requirement when collaboration is enabled:**
+1. Prefer SynapseGrid MCP tools for start/wait/result/cancel/status flows.
+2. Use transcript + meeting summary + artifacts as source of truth.
+3. If collaborative MCP is unavailable, use equivalent CLI commands.
+
+**Preferred MCP flow (recommended):**
+1. `collab_start_session`
+2. `collab_invoke_team`
+3. `collab_wait_run`
+4. `collab_get_result`
+5. Optional diagnostics: `collab_get_transcript`, `collab_get_meeting_log`, `collab_status`
+
+**CLI fallback and operations:**
+```bash
+# Setup/runtime
+acfm agents setup
+acfm agents runtime install-zellij
+acfm agents runtime set auto
+acfm agents doctor --verbose
+
+# Start/run
+acfm agents start --task "design and implement feature X" --mux auto
+acfm agents live
+acfm agents status
+
+# Visibility and artifacts
+acfm agents transcript --role all --limit 80
+acfm agents summary
+acfm agents artifacts --watch --interval 1200
+acfm agents export --format md --out synapse-session.md
+
+# Model management
+acfm agents model list
+acfm agents model choose
+acfm agents model set --role coder provider/model
+
+# Lifecycle
+acfm agents resume
+acfm agents stop
+```
+
+**Collaboration artifacts (deterministic, not prompt-dependent):**
+- `~/.acfm/synapsegrid/<sessionId>/transcript.jsonl`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-log.md`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-summary.md`
+- `~/.acfm/synapsegrid/<sessionId>/turns/*.json`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.ndjson`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.stderr.log`
+- `~/.acfm/synapsegrid/<sessionId>/diagnostics.json`
+
+**Troubleshooting and robust behavior:**
+- Use `acfm agents doctor --verbose` for capability probe diagnostics.
+- In `--mux auto`, runtime prefers zellij and falls back to tmux when zellij startup fails.
+- If model/provider errors appear, validate with `opencode auth list` and `opencode models`.
+- If workers are running but unclear, inspect `logs`, `transcript`, and `artifacts` before restarting.
+
+
 ### OpenSpec Skills (The heart of the framework)
 
 | Skill | Description | Primary Use | Required Before |
@@ -169,7 +244,7 @@ Before proceeding to next phase, verify you have these outputs:
 | Phase 2 | project-index.md exists, exploration notes | [ ] |
 | Phase 3 | proposal.md, specs/, design.md, tasks.md | [ ] |
 | Phase 4 | Tests written, code implemented, tasks marked complete | [ ] |
-| Phase 5 | Verification passed, docs updated, change archived | [ ] |
+| Phase 5 | Verification passed, `vibe-security` audit complete, docs updated, change archived | [ ] |
 
 **Rule 4: Pre-Implementation Safety Check**
 Before `openspec-apply-change`, ALL must be TRUE:
@@ -331,15 +406,17 @@ When starting a project **from scratch**, follow this **MANDATORY** workflow:
     ║      └─ Resolve any issues                   ║
     ║  26. openspec-verify-change                  ║
     ║      └─ Validate against specs               ║
-    ║  27. documentation                           ║
+    ║  27. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  28. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  28. sync-index                              ║
+    ║  29. sync-index                              ║
     ║      └─ Update project documentation         ║
-    ║  29. changelog-generator                     ║
+    ║  30. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  30. ci-deploy                               ║
+    ║  31. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  31. openspec-archive-change                 ║
+    ║  32. openspec-archive-change                 ║
     ║      └─ Archive the change                   ║
     ╚══════════════════════════════════════════════╝
 ```
@@ -457,15 +534,17 @@ When working on an **existing codebase** (adding features, fixing bugs, refactor
     ║      └─ Fix regressions                      ║
     ║  23. openspec-verify-change                  ║
     ║      └─ Final verification                   ║
-    ║  24. documentation                           ║
+    ║  24. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  25. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  25. sync-index (IMPORTANT)                  ║
+    ║  26. sync-index (IMPORTANT)                  ║
     ║      └─ Update docs with new changes         ║
-    ║  26. changelog-generator                     ║
+    ║  27. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  27. ci-deploy                               ║
+    ║  28. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  28. openspec-archive-change                 ║
+    ║  29. openspec-archive-change                 ║
     ║      └─ Archive change                       ║
     ╚══════════════════════════════════════════════╝
 ```

package/framework/web_development/GEMINI.md

@@ -15,6 +15,7 @@ If you attempt to proceed without completing a required step, you MUST STOP and
 | Skill | Description | Primary Use | Required Before |
 |-------|-------------|-------------|-----------------|
 | `secure-coding-cybersecurity` | Detects and prevents security vulnerabilities (SQLi, XSS, command injection, hardcoded secrets). Follows OWASP Top 10 standards. | Secure code validation | `code-maintainability` |
+| `vibe-security` | Final security audit focused on AI-generated/vibe-coded risks (exposed keys, broken access control, auth/payment/data validation gaps). | Final security validation before closure | `openspec-archive-change` |
 | `code-maintainability` | Analyzes code maintainability: duplication, documentation, error handling, naming conventions, SOLID architecture, performance. | Refactoring and standards | `project-constitution` |
 | `error-handling-patterns` | Error handling patterns in multiple languages: exceptions, Result types, retry, circuit breaker, graceful degradation. | Application resilience | `secure-coding-cybersecurity` |
 | `performance-optimizer` | Methodologies for measuring, profiling, and optimizing code (caching, algorithm complexity, resource usage). | Performance Engineering | After Implementation |
@@ -99,6 +100,80 @@ acfm memory stats
 **User communication:** "Memory saved: [brief description]" when auto-saving occurs.
 
 
+
+### SynapseGrid Collaborative MCP Protocol (Optional)
+
+If SynapseGrid is enabled in `acfm init`, AC Framework installs the collaborative MCP server automatically for detected assistants.
+
+**When to delegate to SynapseGrid:**
+- Multi-step features with architecture + implementation + review work
+- Tasks requiring critical analysis before coding (security, API contracts, refactors)
+- Long-running work where transcript, artifacts, and resumability are important
+- Situations where one assistant would benefit from role-based challenge/review
+
+**Role delegation model (what each agent does best):**
+- `planner`: breaks down scope, constraints, approach, acceptance criteria
+- `critic`: challenges assumptions, finds risks/blind spots, proposes safer alternatives
+- `coder`: implements code and applies concrete changes
+- `reviewer`: validates quality, consistency with spec/tasks, and production readiness
+
+**Session-start requirement when collaboration is enabled:**
+1. Prefer SynapseGrid MCP tools for start/wait/result/cancel/status flows.
+2. Use transcript + meeting summary + artifacts as source of truth.
+3. If collaborative MCP is unavailable, use equivalent CLI commands.
+
+**Preferred MCP flow (recommended):**
+1. `collab_start_session`
+2. `collab_invoke_team`
+3. `collab_wait_run`
+4. `collab_get_result`
+5. Optional diagnostics: `collab_get_transcript`, `collab_get_meeting_log`, `collab_status`
+
+**CLI fallback and operations:**
+```bash
+# Setup/runtime
+acfm agents setup
+acfm agents runtime install-zellij
+acfm agents runtime set auto
+acfm agents doctor --verbose
+
+# Start/run
+acfm agents start --task "design and implement feature X" --mux auto
+acfm agents live
+acfm agents status
+
+# Visibility and artifacts
+acfm agents transcript --role all --limit 80
+acfm agents summary
+acfm agents artifacts --watch --interval 1200
+acfm agents export --format md --out synapse-session.md
+
+# Model management
+acfm agents model list
+acfm agents model choose
+acfm agents model set --role coder provider/model
+
+# Lifecycle
+acfm agents resume
+acfm agents stop
+```
+
+**Collaboration artifacts (deterministic, not prompt-dependent):**
+- `~/.acfm/synapsegrid/<sessionId>/transcript.jsonl`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-log.md`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-summary.md`
+- `~/.acfm/synapsegrid/<sessionId>/turns/*.json`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.ndjson`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.stderr.log`
+- `~/.acfm/synapsegrid/<sessionId>/diagnostics.json`
+
+**Troubleshooting and robust behavior:**
+- Use `acfm agents doctor --verbose` for capability probe diagnostics.
+- In `--mux auto`, runtime prefers zellij and falls back to tmux when zellij startup fails.
+- If model/provider errors appear, validate with `opencode auth list` and `opencode models`.
+- If workers are running but unclear, inspect `logs`, `transcript`, and `artifacts` before restarting.
+
+
 ### OpenSpec Skills (The heart of the framework)
 
 | Skill | Description | Primary Use | Required Before |
@@ -169,7 +244,7 @@ Before proceeding to next phase, verify you have these outputs:
 | Phase 2 | project-index.md exists, exploration notes | [ ] |
 | Phase 3 | proposal.md, specs/, design.md, tasks.md | [ ] |
 | Phase 4 | Tests written, code implemented, tasks marked complete | [ ] |
-| Phase 5 | Verification passed, docs updated, change archived | [ ] |
+| Phase 5 | Verification passed, `vibe-security` audit complete, docs updated, change archived | [ ] |
 
 **Rule 4: Pre-Implementation Safety Check**
 Before `openspec-apply-change`, ALL must be TRUE:
@@ -331,15 +406,17 @@ When starting a project **from scratch**, follow this **MANDATORY** workflow:
     ║      └─ Resolve any issues                   ║
     ║  26. openspec-verify-change                  ║
     ║      └─ Validate against specs               ║
-    ║  27. documentation                           ║
+    ║  27. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  28. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  28. sync-index                              ║
+    ║  29. sync-index                              ║
     ║      └─ Update project documentation         ║
-    ║  29. changelog-generator                     ║
+    ║  30. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  30. ci-deploy                               ║
+    ║  31. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  31. openspec-archive-change                 ║
+    ║  32. openspec-archive-change                 ║
     ║      └─ Archive the change                   ║
     ╚══════════════════════════════════════════════╝
 ```
@@ -457,15 +534,17 @@ When working on an **existing codebase** (adding features, fixing bugs, refactor
     ║      └─ Fix regressions                      ║
     ║  23. openspec-verify-change                  ║
     ║      └─ Final verification                   ║
-    ║  24. documentation                           ║
+    ║  24. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  25. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  25. sync-index (IMPORTANT)                  ║
+    ║  26. sync-index (IMPORTANT)                  ║
     ║      └─ Update docs with new changes         ║
-    ║  26. changelog-generator                     ║
+    ║  27. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  27. ci-deploy                               ║
+    ║  28. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  28. openspec-archive-change                 ║
+    ║  29. openspec-archive-change                 ║
     ║      └─ Archive change                       ║
     ╚══════════════════════════════════════════════╝
 ```

package/framework/web_development/copilot-instructions.md

@@ -15,6 +15,7 @@ If you attempt to proceed without completing a required step, you MUST STOP and
 | Skill | Description | Primary Use | Required Before |
 |-------|-------------|-------------|-----------------|
 | `secure-coding-cybersecurity` | Detects and prevents security vulnerabilities (SQLi, XSS, command injection, hardcoded secrets). Follows OWASP Top 10 standards. | Secure code validation | `code-maintainability` |
+| `vibe-security` | Final security audit focused on AI-generated/vibe-coded risks (exposed keys, broken access control, auth/payment/data validation gaps). | Final security validation before closure | `openspec-archive-change` |
 | `code-maintainability` | Analyzes code maintainability: duplication, documentation, error handling, naming conventions, SOLID architecture, performance. | Refactoring and standards | `project-constitution` |
 | `error-handling-patterns` | Error handling patterns in multiple languages: exceptions, Result types, retry, circuit breaker, graceful degradation. | Application resilience | `secure-coding-cybersecurity` |
 | `performance-optimizer` | Methodologies for measuring, profiling, and optimizing code (caching, algorithm complexity, resource usage). | Performance Engineering | After Implementation |
@@ -99,6 +100,80 @@ acfm memory stats
 **User communication:** "Memory saved: [brief description]" when auto-saving occurs.
 
 
+
+### SynapseGrid Collaborative MCP Protocol (Optional)
+
+If SynapseGrid is enabled in `acfm init`, AC Framework installs the collaborative MCP server automatically for detected assistants.
+
+**When to delegate to SynapseGrid:**
+- Multi-step features with architecture + implementation + review work
+- Tasks requiring critical analysis before coding (security, API contracts, refactors)
+- Long-running work where transcript, artifacts, and resumability are important
+- Situations where one assistant would benefit from role-based challenge/review
+
+**Role delegation model (what each agent does best):**
+- `planner`: breaks down scope, constraints, approach, acceptance criteria
+- `critic`: challenges assumptions, finds risks/blind spots, proposes safer alternatives
+- `coder`: implements code and applies concrete changes
+- `reviewer`: validates quality, consistency with spec/tasks, and production readiness
+
+**Session-start requirement when collaboration is enabled:**
+1. Prefer SynapseGrid MCP tools for start/wait/result/cancel/status flows.
+2. Use transcript + meeting summary + artifacts as source of truth.
+3. If collaborative MCP is unavailable, use equivalent CLI commands.
+
+**Preferred MCP flow (recommended):**
+1. `collab_start_session`
+2. `collab_invoke_team`
+3. `collab_wait_run`
+4. `collab_get_result`
+5. Optional diagnostics: `collab_get_transcript`, `collab_get_meeting_log`, `collab_status`
+
+**CLI fallback and operations:**
+```bash
+# Setup/runtime
+acfm agents setup
+acfm agents runtime install-zellij
+acfm agents runtime set auto
+acfm agents doctor --verbose
+
+# Start/run
+acfm agents start --task "design and implement feature X" --mux auto
+acfm agents live
+acfm agents status
+
+# Visibility and artifacts
+acfm agents transcript --role all --limit 80
+acfm agents summary
+acfm agents artifacts --watch --interval 1200
+acfm agents export --format md --out synapse-session.md
+
+# Model management
+acfm agents model list
+acfm agents model choose
+acfm agents model set --role coder provider/model
+
+# Lifecycle
+acfm agents resume
+acfm agents stop
+```
+
+**Collaboration artifacts (deterministic, not prompt-dependent):**
+- `~/.acfm/synapsegrid/<sessionId>/transcript.jsonl`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-log.md`
+- `~/.acfm/synapsegrid/<sessionId>/meeting-summary.md`
+- `~/.acfm/synapsegrid/<sessionId>/turns/*.json`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.ndjson`
+- `~/.acfm/synapsegrid/<sessionId>/turns/raw/*.stderr.log`
+- `~/.acfm/synapsegrid/<sessionId>/diagnostics.json`
+
+**Troubleshooting and robust behavior:**
+- Use `acfm agents doctor --verbose` for capability probe diagnostics.
+- In `--mux auto`, runtime prefers zellij and falls back to tmux when zellij startup fails.
+- If model/provider errors appear, validate with `opencode auth list` and `opencode models`.
+- If workers are running but unclear, inspect `logs`, `transcript`, and `artifacts` before restarting.
+
+
 ### OpenSpec Skills (The heart of the framework)
 
 | Skill | Description | Primary Use | Required Before |
@@ -169,7 +244,7 @@ Before proceeding to next phase, verify you have these outputs:
 | Phase 2 | project-index.md exists, exploration notes | [ ] |
 | Phase 3 | proposal.md, specs/, design.md, tasks.md | [ ] |
 | Phase 4 | Tests written, code implemented, tasks marked complete | [ ] |
-| Phase 5 | Verification passed, docs updated, change archived | [ ] |
+| Phase 5 | Verification passed, `vibe-security` audit complete, docs updated, change archived | [ ] |
 
 **Rule 4: Pre-Implementation Safety Check**
 Before `openspec-apply-change`, ALL must be TRUE:
@@ -331,15 +406,17 @@ When starting a project **from scratch**, follow this **MANDATORY** workflow:
     ║      └─ Resolve any issues                   ║
     ║  26. openspec-verify-change                  ║
     ║      └─ Validate against specs               ║
-    ║  27. documentation                           ║
+    ║  27. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  28. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  28. sync-index                              ║
+    ║  29. sync-index                              ║
     ║      └─ Update project documentation         ║
-    ║  29. changelog-generator                     ║
+    ║  30. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  30. ci-deploy                               ║
+    ║  31. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  31. openspec-archive-change                 ║
+    ║  32. openspec-archive-change                 ║
     ║      └─ Archive the change                   ║
     ╚══════════════════════════════════════════════╝
 ```
@@ -457,15 +534,17 @@ When working on an **existing codebase** (adding features, fixing bugs, refactor
     ║      └─ Fix regressions                      ║
     ║  23. openspec-verify-change                  ║
     ║      └─ Final verification                   ║
-    ║  24. documentation                           ║
+    ║  24. vibe-security                           ║
+    ║      └─ Final security audit before closure  ║
+    ║  25. documentation                           ║
     ║      └─ Generate technical docs & diagrams   ║
-    ║  25. sync-index (IMPORTANT)                  ║
+    ║  26. sync-index (IMPORTANT)                  ║
     ║      └─ Update docs with new changes         ║
-    ║  26. changelog-generator                     ║
+    ║  27. changelog-generator                     ║
     ║      └─ Generate release notes               ║
-    ║  27. ci-deploy                               ║
+    ║  28. ci-deploy                               ║
     ║      └─ Deploy and verify solution           ║
-    ║  28. openspec-archive-change                 ║
+    ║  29. openspec-archive-change                 ║
     ║      └─ Archive change                       ║
     ╚══════════════════════════════════════════════╝
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ac-framework",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "description": "Agentic Coding Framework - Multi-assistant configuration system with OpenSpec workflows",
   "main": "src/index.js",
   "exports": {
@@ -42,16 +42,16 @@
   },
   "homepage": "https://github.com/b4san/AC-framework#readme",
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.27.1",
-    "better-sqlite3": "^11.8.1",
+    "@modelcontextprotocol/sdk": "^1.29.0",
+    "better-sqlite3": "^12.9.0",
     "chalk": "^5.3.0",
-    "commander": "^12.1.0",
+    "commander": "^14.0.3",
     "gradient-string": "^3.0.0",
-    "inquirer": "^12.3.2",
+    "inquirer": "^13.4.3",
     "js-yaml": "^4.1.1",
     "nanospinner": "^1.2.2",
-    "tar": "^7.5.7",
-    "zod": "^4.3.6"
+    "tar": "^7.5.15",
+    "zod": "^4.4.3"
   },
   "type": "module",
   "engines": {

package/src/config/constants.js

@@ -17,16 +17,16 @@ export const ALWAYS_INSTALL = [];
 // When a key module is selected, its bundled companions are auto-installed.
 export const BUNDLED = {
   '.cline': ['.clinerules'],
-  '.antigravity': ['.agent'],  // Antigravity uses .agent/skills/ directory
+  '.antigravity': ['.agents'],  // Antigravity uses .agents/skills/ directory
 };
 
 // Folders that should never appear in the selection list because they are
 // installed automatically as part of a bundled assistant.
-export const HIDDEN_FOLDERS = new Set([...Object.values(BUNDLED).flat(), '.agent']);
+export const HIDDEN_FOLDERS = new Set([...Object.values(BUNDLED).flat(), '.agents']);
 
 // Human-readable descriptions for each module, used in the selection UI.
 export const DESCRIPTIONS = {
-  '.agent': 'Generic Agent Framework',
+  '.agents': 'Generic Agent Framework',
   '.antigravity': 'Google Antigravity IDE (Agent-First)',
   '.amazonq': 'AWS Amazon Q',
   '.augment': 'Augment Code Assistant',
@@ -55,7 +55,7 @@ export const DESCRIPTIONS = {
 
 // Icons for each assistant, used in the selection UI.
 export const ASSISTANT_ICONS = {
-  '.agent': '⊡',
+  '.agents': '⊡',
   '.antigravity': '◉',
   '.amazonq': '◈',
   '.augment': '◇',
@@ -83,6 +83,7 @@ export const ASSISTANT_ICONS = {
 
 export const TEMPLATE_DESCRIPTIONS = {
   new_project: 'Best default for greenfield projects with the full skill catalog.',
+  make_your_own: 'General-purpose base where teams build their own skill repertoire without web-specific specializations.',
   mobile_development: 'Mobile-focused setup with general workflow skills and less web-specific specialization.',
   web_development: 'Web-focused setup with UI, API, testing, performance, and React-oriented guidance.',
 };
@@ -93,6 +94,11 @@ export const TEMPLATE_CAPABILITIES = {
     'Broad skill catalog for app, API, quality, and security work',
     'Best starting point when project type is still flexible',
   ],
+  make_your_own: [
+    'Includes all assistant/CLI and IDE packs from the base template',
+    'Keeps general OpenSpec, quality, security, and documentation skills',
+    'Encourages teams to curate and expand their own reusable skill stack',
+  ],
   mobile_development: [
     'Spec-driven workflow plus general execution and documentation skills',
     'Reduced specialization to keep the template lighter and more adaptable',
@@ -114,6 +120,14 @@ export const TEMPLATE_SKILL_PREVIEWS = {
     'code-review',
     'secure-coding-cybersecurity',
   ],
+  make_your_own: [
+    'brainstorming',
+    'project-index',
+    'spec-clarification',
+    'skill-writer',
+    'find-skills',
+    'sync-index',
+  ],
   mobile_development: [
     'brainstorming',
     'project-index',

package/src/config/ide-mapping.js

@@ -4,7 +4,7 @@
  * (the assistant uses a different mechanism, like .clinerules).
  */
 export const IDE_MD_MAP = {
-  '.agent': 'AGENTS.md',
+  '.agents': 'AGENTS.md',
   '.amazonq': 'AGENTS.md',
   '.augment': 'AGENTS.md',
   '.claude': 'CLAUDE.md',

package/src/services/installer.js

@@ -7,7 +7,7 @@ const __dirname = dirname(fileURLToPath(import.meta.url));
 
 /** Absolute path to the bundled framework/ directory inside this package. */
 export const FRAMEWORK_PATH = resolve(__dirname, '../../framework');
-export const DEFAULT_TEMPLATE = 'new_project';
+export const DEFAULT_TEMPLATE = 'make_your_own';
 export const TEMPLATE_METADATA_FILE = '.acfm-template.json';
 
 function isTemplateDirectory(entry) {
@@ -110,7 +110,7 @@ export async function detectTemplateForModules(modules, frameworkPath = FRAMEWOR
  */
 export async function getSelectableModules(frameworkPath = FRAMEWORK_PATH) {
   const entries = await readdir(frameworkPath, { withFileTypes: true });
-  return entries
+  const physicalModules = entries
     .filter(
       (e) =>
         e.isDirectory() &&
@@ -118,8 +118,18 @@ export async function getSelectableModules(frameworkPath = FRAMEWORK_PATH) {
         !ALWAYS_INSTALL.includes(e.name) &&
         !HIDDEN_FOLDERS.has(e.name),
     )
-    .map((e) => e.name)
-    .sort((a, b) => a.localeCompare(b));
+    .map((e) => e.name);
+
+  // VIRTUAL MODULES:
+  // Add .antigravity to the list if it is not a physical directory,
+  // but only if the template actually contains the bundled target (.agents).
+  const virtualModules = [];
+  const allDirectories = entries.filter((e) => e.isDirectory()).map((e) => e.name);
+  if (!physicalModules.includes('.antigravity') && allDirectories.includes('.agents')) {
+    virtualModules.push('.antigravity');
+  }
+
+  return [...physicalModules, ...virtualModules].sort((a, b) => a.localeCompare(b));
 }
 
 /**
@@ -133,7 +143,13 @@ export function expandWithBundled(selected) {
       bundled.push(...BUNDLED[folder]);
     }
   }
-  return [...selected, ...bundled, ...ALWAYS_INSTALL];
+  const allSet = new Set([...selected, ...bundled, ...ALWAYS_INSTALL]);
+  
+  // Remove pure virtual aliases from installation list.
+  // .antigravity is just an alias for .agents now.
+  allSet.delete('.antigravity');
+  
+  return Array.from(allSet);
 }
 
 /**

package/framework/mobile_development/.agent/skills/sync-index/SKILL.md

@@ -1,35 +0,0 @@
----
-name: sync-index
-description: Keep project documentation (.agents/project-index.md and sub-skills) in sync with codebase changes.
----
-
-# Documentation Sync
-
-## Overview
-
-Documentation drift is a major problem. Use this skill to ensure that the project index and agent guidance files are always up-to-date with the codebase.
-
-## Workflow
-
-1.  **Detect Changes**:
-    *   Ideally run after major feature implementation or refactoring.
-    *   Compare current file structure with `project-index.md`.
-
-2.  **Run Indexer**:
-    *   Execute the `project-index` skill again.
-    *   Verify that new modules/directories are captured.
-    *   Ensure deleted files are removed from documentation.
-
-3.  **Update Guidance**:
-    *   Check `agent-*.md` files in domain directories.
-    *   Update any obsolete instructions.
-    *   Add new patterns discovered during implementation.
-
-4.  **Verify Links**:
-    *   Ensure all links in `README.md` and `AGENTS.md` point to valid locations.
-
-## Output
-
-*   Updated `project-index.md`.
-*   Updated domain-specific agent guides.
-*   Confirmation of documentation sync.