cfsa-antigravity 1.0.0

package/template/.agent/skills/session-continuity/protocols/10-placeholder-verification-gate.md

@@ -0,0 +1,104 @@
+> **Framework context required**: This is a protocol excerpt. Before following these steps, read `.agent/skills/session-continuity/SKILL.md` for the complete framework — including the Adaptive Granularity Rule, Level Hierarchy Reference, Frozen Files concept, and Parallel Claim protocol. Protocol files are reference documents for specific steps, not standalone instructions.
+
+# Placeholder Verification Gate Protocol
+
+## Overview
+
+Specification workflows that read `{{PLACEHOLDER}}`-dependent skill paths must verify those placeholders are filled **before** any skill reads. This prevents spec authoring from running with unfilled stack placeholders, which would produce patterns incompatible with the chosen tech stack.
+
+## When to Use
+
+Add a **Step 0 — Placeholder guard** to any specification workflow that reads `{{PLACEHOLDER}}` values as skill paths. The guard runs before all other steps, including re-run checks and prerequisite validations.
+
+## Key Constraint
+
+**No auto-refire of bootstrap.** The agent stops and tells the user exactly what to run. The guard does not attempt to call `/bootstrap-agents` itself — it emits a HARD STOP with the exact recovery command.
+
+## Four-Part Hard Stop Message Structure
+
+When any placeholder contains literal `{{` characters, emit this message for **each** unfilled placeholder:
+
+> ❌ **Bootstrap incomplete — cannot proceed.**
+>
+> **Unfilled placeholder:** `{{PLACEHOLDER_NAME}}`
+>
+> **Recovery:** If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed [tech decision] value, then run `/bootstrap-agents` with `KEY=<confirmed-value>`. If no architecture design document exists, run `/create-prd-stack` first to confirm tech stack decisions.
+>
+> **Why this matters:** [specific step] cannot produce correct output without this skill — [concrete consequence of proceeding without it].
+
+---
+
+## Per-Workflow Placeholder Mappings
+
+### `create-prd-architecture`
+
+**Frontmatter:** `requires_placeholders: [HOSTING_SKILL, ORM_SKILL, DATABASE_SKILLS]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{HOSTING_SKILL}}` | `/create-prd-stack` when hosting provider is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed hosting provider, then run `/bootstrap-agents HOSTING=<confirmed-provider>`. Otherwise run `/create-prd-stack` first. | Data strategy and schema design steps (Steps 4 and 5) cannot run without the hosting skill — deployment topology decisions will lack provider-specific conventions. |
+| `{{ORM_SKILL}}` | `/create-prd-stack` when ORM is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed ORM, then run `/bootstrap-agents ORM=<confirmed-orm>`. Otherwise run `/create-prd-stack` first. | Migration strategy (Step 5.4) cannot run without the ORM skill — schema conventions and migration patterns will be generic instead of stack-specific. |
+| `{{DATABASE_SKILLS}}` | `/create-prd-stack` when database technology is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed database, then run `/bootstrap-agents DATABASE=<confirmed-db>`. Otherwise run `/create-prd-stack` first. | Data strategy (Step 5) cannot run without the database skill — schema design patterns will be incompatible with the chosen database. |
+
+### `write-architecture-spec-design`
+
+**Frontmatter:** `requires_placeholders: [DATABASE_SKILLS, SECURITY_SKILLS]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{DATABASE_SKILLS}}` | `/create-prd-stack` when database technology is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed database, then run `/bootstrap-agents DATABASE=<confirmed-db>`. Otherwise run `/create-prd-stack` first. | Data model design (Step 4) would produce schema patterns incompatible with the chosen database. |
+| `{{SECURITY_SKILLS}}` | `/create-prd-stack` when security tooling is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed security framework, then run `/bootstrap-agents SECURITY=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Edge case and attack surface analysis (Step 7) would run without the project's security skill, missing stack-specific threat vectors. |
+
+### `write-fe-spec-classify`
+
+**Frontmatter:** `requires_placeholders: [LANGUAGE_SKILL, FRONTEND_FRAMEWORK_SKILL, FRONTEND_DESIGN_SKILL, ACCESSIBILITY_SKILL, STATE_MANAGEMENT_SKILL]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{LANGUAGE_SKILL}}` | `/create-prd-stack` when the primary language is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed language, then run `/bootstrap-agents LANGUAGE=<confirmed-language>`. Otherwise run `/create-prd-stack` first. | FE spec components would be written without the correct language skill, producing patterns incompatible with the chosen language. |
+| `{{FRONTEND_FRAMEWORK_SKILL}}` | `/create-prd-stack` when the frontend framework is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed frontend framework, then run `/bootstrap-agents FRONTEND_FRAMEWORK=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | FE spec components would be written without the correct framework skill, producing patterns incompatible with the chosen framework. |
+| `{{FRONTEND_DESIGN_SKILL}}` | `/create-prd-stack` when the frontend design system is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed design system, then run `/bootstrap-agents FRONTEND_DESIGN=<confirmed-design>`. Otherwise run `/create-prd-stack` first. | FE spec components would be written without the correct design skill, producing visual patterns incompatible with the chosen design system. |
+| `{{ACCESSIBILITY_SKILL}}` | `/create-prd-stack` when accessibility tooling is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed accessibility tooling, then run `/bootstrap-agents ACCESSIBILITY=<confirmed-tooling>`. Otherwise run `/create-prd-stack` first. | FE spec components would lack stack-specific accessibility patterns and WCAG implementation guidance. |
+| `{{STATE_MANAGEMENT_SKILL}}` | `/create-prd-stack` when state management is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed state management library, then run `/bootstrap-agents STATE_MANAGEMENT=<confirmed-library>`. Otherwise run `/create-prd-stack` first. | FE spec components would be written without the correct state management conventions, producing patterns incompatible with the chosen state library. |
+
+---
+
+## Reference Implementation
+
+`write-be-spec-classify.md` Step 2.5 is the canonical example of a correctly implemented placeholder guard. It follows the exact four-part message structure and demonstrates the scan-then-stop pattern.
+
+---
+
+## Additional Per-Workflow Placeholder Mappings
+
+### `create-prd-security`
+
+**Frontmatter:** `requires_placeholders: [SECURITY_SKILLS, AUTH_SKILL]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{SECURITY_SKILLS}}` | `/create-prd-stack` when security tooling is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed security framework, then run `/bootstrap-agents SECURITY=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Security model (Step 6) cannot produce stack-specific threat analysis without the security skill — the model will miss framework-specific attack vectors. |
+| `{{AUTH_SKILL}}` | `/create-prd-stack` when auth provider is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed auth provider, then run `/bootstrap-agents AUTH=<confirmed-provider>`. Otherwise run `/create-prd-stack` first. | Authentication design (Step 6.1) cannot produce correct auth flows without the auth skill — identity provider conventions and token handling will be generic. |
+
+### `create-prd-compile`
+
+**Frontmatter:** `requires_placeholders: [UNIT_TESTING_SKILL, E2E_TESTING_SKILL, CI_CD_SKILL]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{UNIT_TESTING_SKILL}}` | `/create-prd-stack` when the unit testing framework is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed unit testing framework, then run `/bootstrap-agents UNIT_TESTING=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Development methodology (Step 8) cannot document correct test conventions without the unit testing skill — TDD patterns will be generic instead of framework-specific. |
+| `{{E2E_TESTING_SKILL}}` | `/create-prd-stack` when the E2E testing framework is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed E2E testing framework, then run `/bootstrap-agents E2E_TESTING=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Development methodology (Step 8) cannot document correct E2E test conventions without the E2E testing skill — integration test patterns will be generic. |
+| `{{CI_CD_SKILL}}` | `/create-prd-stack` when CI/CD platform is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed CI/CD platform, then run `/bootstrap-agents CI_CD=<confirmed-platform>`. Otherwise run `/create-prd-stack` first. | Phasing strategy (Step 9) cannot produce correct pipeline configuration without the CI/CD skill — deployment and quality gate patterns will lack platform-specific conventions. |
+
+### `write-be-spec-classify`
+
+**Frontmatter:** `requires_placeholders: [LANGUAGE_SKILL, DATABASE_SKILLS, AUTH_SKILL, BACKEND_FRAMEWORK_SKILL, ORM_SKILL, UNIT_TESTING_SKILL]`
+
+| Placeholder | Filled by | Recovery | Why this matters |
+|---|---|---|---|
+| `{{LANGUAGE_SKILL}}` | `/create-prd-stack` when the primary language is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed language, then run `/bootstrap-agents LANGUAGE=<confirmed-language>`. Otherwise run `/create-prd-stack` first. | BE spec code conventions would be written without the correct language skill, producing patterns incompatible with the chosen language. |
+| `{{DATABASE_SKILLS}}` | `/create-prd-stack` when database technology is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed database, then run `/bootstrap-agents DATABASE=<confirmed-db>`. Otherwise run `/create-prd-stack` first. | Schema design and query patterns would be incompatible with the chosen database. |
+| `{{AUTH_SKILL}}` | `/create-prd-stack` when auth provider is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed auth provider, then run `/bootstrap-agents AUTH=<confirmed-provider>`. Otherwise run `/create-prd-stack` first. | Authentication middleware and token handling would use generic patterns instead of provider-specific conventions. |
+| `{{BACKEND_FRAMEWORK_SKILL}}` | `/create-prd-stack` when the backend framework is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed backend framework, then run `/bootstrap-agents BACKEND_FRAMEWORK=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Route definitions, middleware patterns, and request handling would be framework-agnostic instead of following confirmed framework conventions. |
+| `{{ORM_SKILL}}` | `/create-prd-stack` when ORM is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed ORM, then run `/bootstrap-agents ORM=<confirmed-orm>`. Otherwise run `/create-prd-stack` first. | Migration patterns and schema conventions would be generic instead of ORM-specific. |
+| `{{UNIT_TESTING_SKILL}}` | `/create-prd-stack` when the unit testing framework is confirmed | If `docs/plans/*-architecture-design.md` exists, read it and extract the confirmed unit testing framework, then run `/bootstrap-agents UNIT_TESTING=<confirmed-framework>`. Otherwise run `/create-prd-stack` first. | Test writing conventions would use generic patterns instead of framework-specific assertions and utilities. |

package/template/.agent/skills/session-continuity/protocols/ambiguity-gates.md

@@ -0,0 +1,48 @@
+> **Framework context required**: This is a protocol excerpt. Before following these steps, read `.agent/skills/session-continuity/SKILL.md` for the complete framework — including the Adaptive Granularity Rule, Level Hierarchy Reference, Frozen Files concept, and Parallel Claim protocol. Protocol files are reference documents for specific steps, not standalone instructions.
+
+# Ambiguity Gates (Micro + Macro)
+
+> Part of [Session Continuity](../SKILL.md) — read the index for overview, directory structure, and integration points.
+
+**Invoked by**: Every `write-*-spec` workflow, before "Request review"
+
+**Purpose**: Ensure no guesses pass downstream. Two levels:
+
+## Micro Ambiguity Check
+
+Walk **each individual element** in the spec and ask:
+> "Would an implementer need to guess about this?"
+
+| Workflow | What to check |
+|----------|---------------|
+| `/write-architecture-spec` | Each feature, interaction, data model field, access rule, edge case |
+| `/write-be-spec` | Each endpoint, request/response field, error code, schema constraint, middleware rule |
+| `/write-fe-spec` | Each component, prop, interaction, state transition, responsive breakpoint, a11y rule |
+
+For every element where the answer is "yes" → **fix it now**. Add the missing
+detail, type, behavior, or constraint. Don't flag it — resolve it.
+
+For every element where the answer is "no" — apply the **two-implementer test**: *"Would two different developers, reading only this spec with no other context, make the same implementation decision for this element?"* If the answer is "probably not" or "maybe not" — fix it now. The bar is not "text exists" — it is "unambiguous to any implementer reading cold."
+
+## Macro Ambiguity Check
+
+Step back and ask about the **entire spec**:
+> "Does the next downstream phase have everything it needs?"
+
+| Workflow | Downstream question |
+|----------|---------------------|
+| `/write-architecture-spec` | Would the BE spec writer need to guess anything from this IA shard? |
+| `/write-be-spec` | Would the FE spec writer need to guess anything from this BE spec? |
+| `/write-fe-spec` | Would an implementer running `/implement-slice` need to guess anything? |
+
+If the answer is "yes" → **fix it now**. The spec is not complete until the
+downstream phase can work from it without assumptions.
+
+## Relationship to `/audit-ambiguity`
+
+The ambiguity gates are **inline, lightweight, fix-it-now** checks. The
+`/audit-ambiguity` workflow is a **standalone, scored, report-generating**
+audit you run across multiple documents at once. They complement each other:
+
+- Gates: prevent ambiguity from entering (at write time)
+- Audit: detect ambiguity that slipped through (after the fact)

package/template/.agent/skills/skill-creator/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/template/.agent/skills/skill-creator/README.md

@@ -0,0 +1,270 @@
+# skill-creator
+
+**Automate CLI skill creation with best practices built-in.**
+
+## What It Does
+
+The skill-creator automates the entire workflow of creating new CLI skills for GitHub Copilot CLI and Claude Code. It guides you through brainstorming, applies standardized templates, validates content quality, and handles installation—all while following Anthropic's official best practices.
+
+## Key Features
+
+- **🎯 Interactive Brainstorming** - Collaborative session to define skill purpose and scope
+- **✨ Template Automation** - Automatic file generation with zero manual configuration
+- **🔍 Quality Validation** - Built-in checks for YAML, content quality, and writing style
+- **📦 Flexible Installation** - Choose repository-only, global, or hybrid installation
+- **📊 Visual Progress Bar** - Real-time progress indicator showing completion status (e.g., `[████████████░░░░░░] 60% - Step 3/5`)
+- **🔗 Prompt Engineer Integration** - Optional enhancement using prompt-engineer skill
+
+## When to Use
+
+Use this skill when you want to:
+- Create a new CLI skill following official standards
+- Extend CLI functionality with custom capabilities
+- Package domain knowledge into a reusable skill format
+- Automate repetitive CLI tasks with a custom skill
+- Install skills locally or globally across your system
+
+## Installation
+
+### Prerequisites
+
+This skill is part of the `cli-ai-skills` repository. To use it:
+
+```bash
+# Clone the repository
+git clone https://github.com/yourusername/cli-ai-skills.git
+cd cli-ai-skills
+```
+
+### Install Globally (Recommended)
+
+Install via symlinks to make the skill available everywhere:
+
+```bash
+# For GitHub Copilot CLI
+ln -sf "$(pwd)/.github/skills/skill-creator" ~/.copilot/skills/skill-creator
+
+# For Claude Code
+ln -sf "$(pwd)/.claude/skills/skill-creator" ~/.claude/skills/skill-creator
+```
+
+**Benefits of global installation:**
+- Works in any directory
+- Auto-updates when you `git pull` the repository
+- No configuration files needed
+
+### Repository-Only Installation
+
+If you prefer to use the skill only within this repository, no installation is needed. The skill will be available when working in the `cli-ai-skills` directory.
+
+## Usage
+
+### Basic Skill Creation
+
+Simply ask the CLI to create a new skill:
+
+```bash
+# GitHub Copilot CLI
+gh copilot "create a new skill for debugging Python errors"
+
+# Claude Code
+claude "create a skill that helps with git workflows"
+```
+
+The skill will guide you through with visual progress tracking:
+1. **Brainstorming** (20%) - Define purpose, triggers, and type
+2. **Prompt Enhancement** (40%, optional) - Enhance with prompt-engineer skill
+3. **File Generation** (60%) - Create files from templates
+4. **Validation** (80%) - Check quality and standards
+5. **Installation** (100%) - Choose local, global, or both
+
+Each phase displays a progress bar:
+```
+[████████████░░░░░░] 60% - Step 3/5: File Generation
+```
+
+### Advanced Usage
+
+#### Create Code Generation Skill
+
+```bash
+"Create a code skill that generates React components from descriptions"
+```
+
+The skill will:
+- Use the specialized `code-skill-template.md`
+- Ask about specific frameworks (React, Vue, etc.)
+- Include code examples in the `examples/` folder
+
+#### Create Documentation Skill
+
+```bash
+"Build a skill that writes API documentation from code"
+```
+
+The skill will:
+- Use `documentation-skill-template.md`
+- Ask about documentation formats
+- Set up references for style guides
+
+#### Install for Specific Platform
+
+```bash
+"Create a skill for Copilot only that analyzes TypeScript errors"
+```
+
+The skill will:
+- Generate files only in `.github/skills/`
+- Skip Claude-specific installation
+- Validate against Copilot requirements
+
+## Example Walkthrough
+
+Here's what creating a skill looks like:
+
+```
+You: "create a skill for database schema migrations"
+
+[████░░░░░░░░░░░░░░] 20% - Step 1/5: Brainstorming & Planning
+
+What should this skill do?
+> Helps users create and manage database schema migrations safely
+
+When should it trigger? (3-5 phrases)
+> "create migration", "generate schema change", "migrate database"
+
+What type of skill?
+> [×] General purpose
+
+Which platforms?
+> [×] Both (Copilot + Claude)
+
+[... continues through all phases ...]
+
+🎉 Skill created successfully!
+
+📦 Skill Name: database-migration
+📁 Location: .github/skills/database-migration/
+🔗 Installed: Global (Copilot + Claude)
+```
+
+## File Structure
+
+When you create a skill, this structure is generated:
+
+```
+.github/skills/your-skill-name/
+├── SKILL.md              # Main skill instructions (1.5-2k words)
+├── README.md             # User-facing documentation (this file)
+├── references/           # Detailed guides (2k-5k words each)
+│   └── (empty, ready for extended docs)
+├── examples/             # Working code samples
+│   └── (empty, ready for examples)
+└── scripts/              # Executable utilities
+    └── (empty, ready for automation)
+```
+
+## Configuration
+
+**No configuration needed!** This skill uses runtime discovery to:
+- Detect installed platforms (Copilot CLI, Claude Code)
+- Find repository root automatically
+- Extract author info from git config
+- Determine optimal file locations
+
+## Validation
+
+Every skill created is automatically validated for:
+- ✅ **YAML Frontmatter** - Required fields and format
+- ✅ **Description Format** - Third-person, trigger phrases
+- ✅ **Word Count** - 1,500-2,000 ideal, under 5,000 max
+- ✅ **Writing Style** - Imperative form, no second-person
+- ✅ **Progressive Disclosure** - Proper content organization
+
+## Frameworks Used
+
+This skill leverages several established methodologies:
+
+- **Progressive Disclosure** - 3-level content hierarchy (metadata → SKILL.md → bundled resources)
+- **Bundled Resources Pattern** - References, examples, and scripts as separate files
+- **Anthropic Best Practices** - Official skill development standards
+- **Zero-Config Design** - Runtime discovery, no hardcoded values
+- **Template-Driven Generation** - Consistent structure across all skills
+
+## Troubleshooting
+
+### "Template not found" Error
+
+Ensure you're in the `cli-ai-skills` repository or have cloned it:
+
+```bash
+git clone https://github.com/yourusername/cli-ai-skills.git
+cd cli-ai-skills
+```
+
+### "Platform not detected" Warning
+
+If platforms aren't detected:
+1. Choose "Repository only" installation
+2. Manually specify platform during setup
+3. Install globally later using provided commands
+
+### Validation Failures
+
+If validation finds issues:
+- Review suggestions in the output
+- Choose automatic fixes for common problems
+- Manually edit files for complex issues
+- Re-run validation: `scripts/validate-skill-yaml.sh .github/skills/your-skill`
+
+## Advanced Features
+
+### Prompt Engineer Integration
+
+Enhance your skill descriptions with AI:
+1. Enable during Phase 2 (Prompt Refinement)
+2. Skill will invoke `prompt-engineer` automatically
+3. Review enhanced output before proceeding
+
+### Bundled Resources
+
+For complex skills, use bundled resources:
+- **references/** - Detailed documentation (no word limit)
+- **examples/** - Working code samples users can run
+- **scripts/** - Automation utilities loaded on demand
+
+### Version Management
+
+Update existing skills:
+```bash
+scripts/update-skill-version.sh your-skill-name 1.1.0
+```
+
+## Contributing
+
+Created a useful skill? Share it:
+1. Ensure validation passes
+2. Add usage examples
+3. Update main README.md
+4. Submit a pull request
+
+## Resources
+
+- **Writing Style Guide:** `resources/templates/writing-style-guide.md`
+- **Anthropic Official Guide:** https://github.com/anthropics/claude-plugins-official
+- **Templates Directory:** `resources/templates/`
+- **Validation Scripts:** `scripts/validate-*.sh`
+
+## Support
+
+For issues or questions:
+- Check existing skills in `.github/skills/` for examples
+- Review `resources/skills-development.md` for methodology
+- Open an issue in the repository
+
+---
+
+**Version:** 1.1.0  
+**Platform:** GitHub Copilot CLI, Claude Code  
+**Author:** Eric Andrade  
+**Last Updated:** 2026-02-01