[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FSRRPCWTPPBTFMKPFEQTV":3,"skill-same:01M75FSRRPCWTPPBTFMKPFEQTV":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75FSRRPCWTPPBTFMKPFEQTV","ogt-docs-create",null,"Create new documentation entities in the docs-first system. Routes to specialized creation sub-skills for tasks, definitions, rules, features, and social content. Use when adding any new documentation.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Feduardou24\u002Fogt-docs-create\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ogt-docs-create\ndescription: Create new documentation entities in the docs-first system. Routes to specialized creation sub-skills for tasks, definitions, rules, features, and social content. Use when adding any new documentation.\n---\n\n# OGT Docs - Create\n\nRoot skill for creating new documentation entities.\n\n## Overview\n\nThis skill routes to specialized creation workflows based on what type of document you're creating. Every entity becomes a folder with appropriate files and signals.\n\n```mermaid\nflowchart TB\n    CREATE[\"ogt-docs-create\"] --> TASK[\"ogt-docs-create-task\"]\n    CREATE --> DEF[\"ogt-docs-define\"]\n    CREATE --> RULE[\"ogt-docs-rules\"]\n    CREATE --> SOCIAL[\"ogt-docs-create-social\"]\n    CREATE --> CHANGE[\"ogt-docs-changelog\"]\n\n    TASK --> |folder| PENDING[\"docs\u002Ftodo\u002Fpending\u002F\"]\n    DEF --> |folder| DEFINE[\"docs\u002Fdefine\u002F\"]\n    RULE --> |folder| RULES[\"docs\u002Frules\u002F\"]\n    SOCIAL --> |folder| CONTENT[\"docs\u002Fcontent\u002F\"]\n    CHANGE --> |file| CHANGELOG[\"CHANGELOG.md\"]\n```\n\n## When to Use\n\n- Creating new tasks\n- Adding definitions (features, code, business, etc.)\n- Establishing new rules\n- Creating social\u002Fmarketing content\n- Updating changelog\n\n## Quick Reference\n\n| Creating      | Sub-Skill                   | Target                 |\n| ------------- | --------------------------- | ---------------------- |\n| Task          | `ogt-docs-create-task`      | docs\u002Ftodo\u002Fpending\u002F     |\n| Feature       | `ogt-docs-define-feature`   | docs\u002Fdefine\u002Ffeatures\u002F  |\n| Business def  | `ogt-docs-define-business`  | docs\u002Fdefine\u002Fbusiness\u002F  |\n| Code def      | `ogt-docs-define-code`      | docs\u002Fdefine\u002Fcode\u002F      |\n| Marketing def | `ogt-docs-define-marketing` | docs\u002Fdefine\u002Fmarketing\u002F |\n| Branding def  | `ogt-docs-define-branding`  | docs\u002Fdefine\u002Fbranding\u002F  |\n| Tool doc      | `ogt-docs-define-tools`     | docs\u002Fdefine\u002Ftools\u002F     |\n| Code rule     | `ogt-docs-rules-code`       | docs\u002Frules\u002Fcode\u002F       |\n| Git rule      | `ogt-docs-rules-git`        | docs\u002Frules\u002Fgit\u002F        |\n| Social post   | `ogt-docs-create-social`    | docs\u002Fcontent\u002Fsocial\u002F   |\n| Changelog     | `ogt-docs-changelog`        | CHANGELOG.md           |\n\n---\n\n## Creation Workflow\n\nAll creation follows the same pattern:\n\n```mermaid\nflowchart LR\n    A[Identify Type] --> B[Create Folder]\n    B --> C[Copy Template]\n    C --> D[Fill Content]\n    D --> E[Add Signals]\n    E --> F[Verify Structure]\n```\n\n### Step 1: Identify Type\n\nDetermine what you're creating:\n\n| If you need to...          | Create a...     | Location              |\n| -------------------------- | --------------- | --------------------- |\n| Track work to do           | Task            | docs\u002Ftodo\u002Fpending\u002F    |\n| Document a product feature | Feature         | docs\u002Fdefine\u002Ffeatures\u002F |\n| Document code architecture | Code definition | docs\u002Fdefine\u002Fcode\u002F     |\n| Establish coding standard  | Code rule       | docs\u002Frules\u002Fcode\u002F      |\n| Record what changed        | Changelog entry | CHANGELOG.md          |\n\n### Step 2: Create Folder\n\n```bash\n# Use slug format: lowercase, hyphens, no spaces\nmkdir -p docs\u002F{section}\u002F{category}\u002F{slug}\n\n# Examples\nmkdir -p docs\u002Ftodo\u002Fpending\u002Fuser-auth-flow\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002Fdark-mode\nmkdir -p docs\u002Frules\u002Fcode\u002Ferror-handling\n```\n\n### Step 3: Copy Template\n\n```bash\n# Copy appropriate template\ncp docs\u002F_templates\u002F{type}.md docs\u002F{path}\u002F{slug}\u002F{type}.md\n\n# Examples\ncp docs\u002F_templates\u002Ftask.md docs\u002Ftodo\u002Fpending\u002Fuser-auth-flow\u002Ftask.md\ncp docs\u002F_templates\u002Ffeature.md docs\u002Fdefine\u002Ffeatures\u002Fdark-mode\u002Ffeature.md\ncp docs\u002F_templates\u002Frule.md docs\u002Frules\u002Fcode\u002Ferror-handling\u002Frule.md\n```\n\n### Step 4: Fill Content\n\nEdit the template with actual content. See sub-skill documentation for required sections.\n\n### Step 5: Add Signals\n\n```bash\n# Common signals\necho '{\"schema\": \"1.0\", \"created\": \"'$(date -Iseconds)'\"}' > {folder}\u002F.version\n\n# Type-specific signals\necho \"high\" > docs\u002Ftodo\u002Fpending\u002F{task}\u002F.priority\ntouch docs\u002Frules\u002Fcode\u002F{rule}\u002F.enforced_by\n```\n\n### Step 6: Verify Structure\n\n```bash\n# Verify folder has required files\nls -la docs\u002F{path}\u002F{slug}\u002F\n\n# Expected output example for task:\n# task.md\n# .version\n# .priority\n```\n\n---\n\n## Templates Overview\n\n### Task Template\n\n```markdown\n# Task: {Title}\n\n## Summary\n\n{What and why}\n\n## Objectives\n\n- Objective 1\n- Objective 2\n\n## Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Dependencies\n\n{None or list}\n\n## Estimated Effort\n\n{Size} ({time})\n```\n\n### Feature Template\n\n```markdown\n# Feature: {Name}\n\n## Summary\n\n{What the feature does}\n\n## User Stories\n\nAs a {user}, I want to {action}, so that {benefit}.\n\n## Scope\n\n### In Scope\n\n- Item 1\n\n### Out of Scope\n\n- Item 1\n\n## Success Metrics\n\n- Metric 1\n```\n\n### Definition Template\n\n```markdown\n# {Name}\n\n## Summary\n\n{One paragraph}\n\n## Details\n\n{Full explanation}\n\n## Examples\n\n{Examples}\n\n## Related\n\n- {Links}\n```\n\n### Rule Template\n\n```markdown\n# Rule: {Name}\n\n## Summary\n\n{One sentence}\n\n## Rationale\n\n{Why}\n\n## The Rule\n\n{MUST\u002FSHOULD\u002FMAY statements}\n\n## Examples\n\n### Correct\n\n{example}\n\n### Incorrect\n\n{example}\n\n## Enforcement\n\n{How enforced}\n```\n\n---\n\n## Batch Creation\n\nCreate multiple related items at once:\n\n```bash\n#!\u002Fbin\u002Fbash\n# create-feature-with-tasks.sh\n\nFEATURE=$1\n\n# Create feature definition\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002F$FEATURE\ncat > docs\u002Fdefine\u002Ffeatures\u002F$FEATURE\u002Ffeature.md \u003C\u003C EOF\n# Feature: $(echo $FEATURE | tr '-' ' ' | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg')\n\n## Summary\n\nTODO: Add summary\n\n## User Stories\n\nAs a user, I want to TODO, so that TODO.\nEOF\n\n# Create initial tasks\nfor task in \"design\" \"implement\" \"test\" \"document\"; do\n  mkdir -p docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\n  cat > docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\u002Ftask.md \u003C\u003C EOF\n# Task: $(echo $FEATURE | tr '-' ' ' | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg') - $(echo $task | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg')\n\n## Summary\n\n${task^} the $FEATURE feature.\n\n## Objectives\n\n- TODO\n\n## Acceptance Criteria\n\n- [ ] TODO\nEOF\n  echo \"medium\" > docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\u002F.priority\ndone\n\necho \"Created feature: $FEATURE\"\necho \"Created tasks: ${FEATURE}-design, ${FEATURE}-implement, ${FEATURE}-test, ${FEATURE}-document\"\n```\n\nUsage:\n\n```bash\n.\u002Fcreate-feature-with-tasks.sh dark-mode\n```\n\n---\n\n## Naming Conventions\n\n### Slug Format\n\nAll folder names use slug format:\n\n| Rule               | Example                          |\n| ------------------ | -------------------------------- |\n| Lowercase          | `user-auth` not `User-Auth`      |\n| Hyphens for spaces | `dark-mode` not `dark_mode`      |\n| No special chars   | `oauth2` not `oauth2.0`          |\n| Descriptive        | `steam-oauth-provider` not `sop` |\n| Under 30 chars     | Keep it readable                 |\n\n### Good Names\n\n```\ndocs\u002Ftodo\u002Fpending\u002Fadd-steam-oauth\ndocs\u002Fdefine\u002Ffeatures\u002Fdark-mode-toggle\ndocs\u002Frules\u002Fcode\u002Fno-implicit-any\n```\n\n### Bad Names\n\n```\ndocs\u002Ftodo\u002Fpending\u002FAdd Steam OAuth          # Spaces, caps\ndocs\u002Fdefine\u002Ffeatures\u002Fdark_mode_toggle      # Underscores\ndocs\u002Frules\u002Fcode\u002Frule1                      # Not descriptive\n```\n\n---\n\n## Validation\n\nAfter creating any document:\n\n### Check Required Files\n\n```bash\n# Task\ntest -f docs\u002Ftodo\u002Fpending\u002F{slug}\u002Ftask.md || echo \"MISSING: task.md\"\ntest -f docs\u002Ftodo\u002Fpending\u002F{slug}\u002F.priority || echo \"MISSING: .priority\"\n\n# Feature\ntest -f docs\u002Fdefine\u002Ffeatures\u002F{slug}\u002Ffeature.md || echo \"MISSING: feature.md\"\ntest -f docs\u002Fdefine\u002Ffeatures\u002F{slug}\u002Fmvp.md || echo \"MISSING: mvp.md\"\n\n# Rule\ntest -f docs\u002Frules\u002F{category}\u002F{slug}\u002Frule.md || echo \"MISSING: rule.md\"\ntest -f docs\u002Frules\u002F{category}\u002F{slug}\u002F.enforced_by || echo \"MISSING: .enforced_by\"\n```\n\n### Check Required Sections\n\n```bash\n# For any markdown file, check for required headings\nfile=$1\nrequired=(\"## Summary\" \"## Objectives\" \"## Acceptance Criteria\")\n\nfor section in \"${required[@]}\"; do\n  grep -q \"$section\" \"$file\" || echo \"MISSING: $section in $file\"\ndone\n```\n\n---\n\n## Common Creation Patterns\n\n### New Feature Flow\n\n1. Create feature definition\n2. Create mvp.md defining scope\n3. Create phase_0.md for initial work\n4. Create tasks for phase_0\n\n```bash\n# 1. Feature folder\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002Fsearch\n\n# 2. Feature definition\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Ffeature.md \u003C\u003C 'EOF'\n# Feature: Global Search\n\n## Summary\nFuzzy search across all content types.\nEOF\n\n# 3. MVP scope\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Fmvp.md \u003C\u003C 'EOF'\n# MVP: Global Search\n\n## In MVP\n- Phase 0 only\n\n## Definition of Done\n- Search returns results in \u003C100ms\n- Fuzzy matching works\nEOF\n\n# 4. Phase 0\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Fphase_0.md \u003C\u003C 'EOF'\n# Phase 0: Basic Search\n\n## Deliverables\n- MiniSearch integration\n- Global search component\nEOF\n\n# 5. Tasks\nmkdir -p docs\u002Ftodo\u002Fpending\u002Fsearch-minisearch-setup\n# ... create task\n```\n\n### New Rule Flow\n\n1. Identify pattern to standardize\n2. Create rule folder\n3. Write rule with examples\n4. Configure enforcement\n5. Announce to team\n\n```bash\n# 1. Rule folder\nmkdir -p docs\u002Frules\u002Fcode\u002Fasync-await\n\n# 2. Rule definition\ncat > docs\u002Frules\u002Fcode\u002Fasync-await\u002Frule.md \u003C\u003C 'EOF'\n# Rule: Prefer async\u002Fawait\n\n## Summary\nSHOULD use async\u002Fawait over .then() chains.\n\n## Rationale\nImproved readability and error handling.\n\n## The Rule\n...\nEOF\n\n# 3. Examples\ncat > docs\u002Frules\u002Fcode\u002Fasync-await\u002Fexamples.md \u003C\u003C 'EOF'\n# Examples\n...\nEOF\n\n# 4. Enforcement\necho \"eslint prefer-async-await\" > docs\u002Frules\u002Fcode\u002Fasync-await\u002F.enforced_by\n\n# 5. Configure ESLint\n# Edit .eslintrc.js\n```\n\n---\n\n## Signal Files Quick Reference\n\n| Signal         | Used For    | Content                  |\n| -------------- | ----------- | ------------------------ |\n| `.version`     | All         | JSON schema version      |\n| `.priority`    | Tasks       | critical\u002Fhigh\u002Fmedium\u002Flow |\n| `.enforced_by` | Rules       | List of tools            |\n| `.status`      | Definitions | draft\u002Freview\u002Fapproved    |\n| `.created_at`  | All         | ISO timestamp            |\n| `.created_by`  | All         | Author name              |\n\n---\n\n## Creation Checklist\n\nBefore finalizing any created document:\n\n- [ ] Folder uses slug format\n- [ ] Primary file exists (task.md, feature.md, etc.)\n- [ ] .version signal added\n- [ ] Required sections present\n- [ ] No TODO placeholders remain\n- [ ] Links are valid\n- [ ] Spelling\u002Fgrammar checked\n- [ ] Related documents cross-referenced\n","# OGT Docs - Create\n\nRoot skill for creating new documentation entities.\n\n## Overview\n\nThis skill routes to specialized creation workflows based on what type of document you're creating. Every entity becomes a folder with appropriate files and signals.\n\n```mermaid\nflowchart TB\n    CREATE[\"ogt-docs-create\"] --> TASK[\"ogt-docs-create-task\"]\n    CREATE --> DEF[\"ogt-docs-define\"]\n    CREATE --> RULE[\"ogt-docs-rules\"]\n    CREATE --> SOCIAL[\"ogt-docs-create-social\"]\n    CREATE --> CHANGE[\"ogt-docs-changelog\"]\n\n    TASK --> |folder| PENDING[\"docs\u002Ftodo\u002Fpending\u002F\"]\n    DEF --> |folder| DEFINE[\"docs\u002Fdefine\u002F\"]\n    RULE --> |folder| RULES[\"docs\u002Frules\u002F\"]\n    SOCIAL --> |folder| CONTENT[\"docs\u002Fcontent\u002F\"]\n    CHANGE --> |file| CHANGELOG[\"CHANGELOG.md\"]\n```\n\n## When to Use\n\n- Creating new tasks\n- Adding definitions (features, code, business, etc.)\n- Establishing new rules\n- Creating social\u002Fmarketing content\n- Updating changelog\n\n## Quick Reference\n\n| Creating      | Sub-Skill                   | Target                 |\n| ------------- | --------------------------- | ---------------------- |\n| Task          | `ogt-docs-create-task`      | docs\u002Ftodo\u002Fpending\u002F     |\n| Feature       | `ogt-docs-define-feature`   | docs\u002Fdefine\u002Ffeatures\u002F  |\n| Business def  | `ogt-docs-define-business`  | docs\u002Fdefine\u002Fbusiness\u002F  |\n| Code def      | `ogt-docs-define-code`      | docs\u002Fdefine\u002Fcode\u002F      |\n| Marketing def | `ogt-docs-define-marketing` | docs\u002Fdefine\u002Fmarketing\u002F |\n| Branding def  | `ogt-docs-define-branding`  | docs\u002Fdefine\u002Fbranding\u002F  |\n| Tool doc      | `ogt-docs-define-tools`     | docs\u002Fdefine\u002Ftools\u002F     |\n| Code rule     | `ogt-docs-rules-code`       | docs\u002Frules\u002Fcode\u002F       |\n| Git rule      | `ogt-docs-rules-git`        | docs\u002Frules\u002Fgit\u002F        |\n| Social post   | `ogt-docs-create-social`    | docs\u002Fcontent\u002Fsocial\u002F   |\n| Changelog     | `ogt-docs-changelog`        | CHANGELOG.md           |\n\n---\n\n## Creation Workflow\n\nAll creation follows the same pattern:\n\n```mermaid\nflowchart LR\n    A[Identify Type] --> B[Create Folder]\n    B --> C[Copy Template]\n    C --> D[Fill Content]\n    D --> E[Add Signals]\n    E --> F[Verify Structure]\n```\n\n### Step 1: Identify Type\n\nDetermine what you're creating:\n\n| If you need to...          | Create a...     | Location              |\n| -------------------------- | --------------- | --------------------- |\n| Track work to do           | Task            | docs\u002Ftodo\u002Fpending\u002F    |\n| Document a product feature | Feature         | docs\u002Fdefine\u002Ffeatures\u002F |\n| Document code architecture | Code definition | docs\u002Fdefine\u002Fcode\u002F     |\n| Establish coding standard  | Code rule       | docs\u002Frules\u002Fcode\u002F      |\n| Record what changed        | Changelog entry | CHANGELOG.md          |\n\n### Step 2: Create Folder\n\n```bash\n# Use slug format: lowercase, hyphens, no spaces\nmkdir -p docs\u002F{section}\u002F{category}\u002F{slug}\n\n# Examples\nmkdir -p docs\u002Ftodo\u002Fpending\u002Fuser-auth-flow\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002Fdark-mode\nmkdir -p docs\u002Frules\u002Fcode\u002Ferror-handling\n```\n\n### Step 3: Copy Template\n\n```bash\n# Copy appropriate template\ncp docs\u002F_templates\u002F{type}.md docs\u002F{path}\u002F{slug}\u002F{type}.md\n\n# Examples\ncp docs\u002F_templates\u002Ftask.md docs\u002Ftodo\u002Fpending\u002Fuser-auth-flow\u002Ftask.md\ncp docs\u002F_templates\u002Ffeature.md docs\u002Fdefine\u002Ffeatures\u002Fdark-mode\u002Ffeature.md\ncp docs\u002F_templates\u002Frule.md docs\u002Frules\u002Fcode\u002Ferror-handling\u002Frule.md\n```\n\n### Step 4: Fill Content\n\nEdit the template with actual content. See sub-skill documentation for required sections.\n\n### Step 5: Add Signals\n\n```bash\n# Common signals\necho '{\"schema\": \"1.0\", \"created\": \"'$(date -Iseconds)'\"}' > {folder}\u002F.version\n\n# Type-specific signals\necho \"high\" > docs\u002Ftodo\u002Fpending\u002F{task}\u002F.priority\ntouch docs\u002Frules\u002Fcode\u002F{rule}\u002F.enforced_by\n```\n\n### Step 6: Verify Structure\n\n```bash\n# Verify folder has required files\nls -la docs\u002F{path}\u002F{slug}\u002F\n\n# Expected output example for task:\n# task.md\n# .version\n# .priority\n```\n\n---\n\n## Templates Overview\n\n### Task Template\n\n```markdown\n# Task: {Title}\n\n## Summary\n\n{What and why}\n\n## Objectives\n\n- Objective 1\n- Objective 2\n\n## Acceptance Criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Dependencies\n\n{None or list}\n\n## Estimated Effort\n\n{Size} ({time})\n```\n\n### Feature Template\n\n```markdown\n# Feature: {Name}\n\n## Summary\n\n{What the feature does}\n\n## User Stories\n\nAs a {user}, I want to {action}, so that {benefit}.\n\n## Scope\n\n### In Scope\n\n- Item 1\n\n### Out of Scope\n\n- Item 1\n\n## Success Metrics\n\n- Metric 1\n```\n\n### Definition Template\n\n```markdown\n# {Name}\n\n## Summary\n\n{One paragraph}\n\n## Details\n\n{Full explanation}\n\n## Examples\n\n{Examples}\n\n## Related\n\n- {Links}\n```\n\n### Rule Template\n\n```markdown\n# Rule: {Name}\n\n## Summary\n\n{One sentence}\n\n## Rationale\n\n{Why}\n\n## The Rule\n\n{MUST\u002FSHOULD\u002FMAY statements}\n\n## Examples\n\n### Correct\n\n{example}\n\n### Incorrect\n\n{example}\n\n## Enforcement\n\n{How enforced}\n```\n\n---\n\n## Batch Creation\n\nCreate multiple related items at once:\n\n```bash\n#!\u002Fbin\u002Fbash\n# create-feature-with-tasks.sh\n\nFEATURE=$1\n\n# Create feature definition\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002F$FEATURE\ncat > docs\u002Fdefine\u002Ffeatures\u002F$FEATURE\u002Ffeature.md \u003C\u003C EOF\n# Feature: $(echo $FEATURE | tr '-' ' ' | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg')\n\n## Summary\n\nTODO: Add summary\n\n## User Stories\n\nAs a user, I want to TODO, so that TODO.\nEOF\n\n# Create initial tasks\nfor task in \"design\" \"implement\" \"test\" \"document\"; do\n  mkdir -p docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\n  cat > docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\u002Ftask.md \u003C\u003C EOF\n# Task: $(echo $FEATURE | tr '-' ' ' | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg') - $(echo $task | sed 's\u002F\\b\\(.\\)\u002F\\u\\1\u002Fg')\n\n## Summary\n\n${task^} the $FEATURE feature.\n\n## Objectives\n\n- TODO\n\n## Acceptance Criteria\n\n- [ ] TODO\nEOF\n  echo \"medium\" > docs\u002Ftodo\u002Fpending\u002F${FEATURE}-${task}\u002F.priority\ndone\n\necho \"Created feature: $FEATURE\"\necho \"Created tasks: ${FEATURE}-design, ${FEATURE}-implement, ${FEATURE}-test, ${FEATURE}-document\"\n```\n\nUsage:\n\n```bash\n.\u002Fcreate-feature-with-tasks.sh dark-mode\n```\n\n---\n\n## Naming Conventions\n\n### Slug Format\n\nAll folder names use slug format:\n\n| Rule               | Example                          |\n| ------------------ | -------------------------------- |\n| Lowercase          | `user-auth` not `User-Auth`      |\n| Hyphens for spaces | `dark-mode` not `dark_mode`      |\n| No special chars   | `oauth2` not `oauth2.0`          |\n| Descriptive        | `steam-oauth-provider` not `sop` |\n| Under 30 chars     | Keep it readable                 |\n\n### Good Names\n\n```\ndocs\u002Ftodo\u002Fpending\u002Fadd-steam-oauth\ndocs\u002Fdefine\u002Ffeatures\u002Fdark-mode-toggle\ndocs\u002Frules\u002Fcode\u002Fno-implicit-any\n```\n\n### Bad Names\n\n```\ndocs\u002Ftodo\u002Fpending\u002FAdd Steam OAuth          # Spaces, caps\ndocs\u002Fdefine\u002Ffeatures\u002Fdark_mode_toggle      # Underscores\ndocs\u002Frules\u002Fcode\u002Frule1                      # Not descriptive\n```\n\n---\n\n## Validation\n\nAfter creating any document:\n\n### Check Required Files\n\n```bash\n# Task\ntest -f docs\u002Ftodo\u002Fpending\u002F{slug}\u002Ftask.md || echo \"MISSING: task.md\"\ntest -f docs\u002Ftodo\u002Fpending\u002F{slug}\u002F.priority || echo \"MISSING: .priority\"\n\n# Feature\ntest -f docs\u002Fdefine\u002Ffeatures\u002F{slug}\u002Ffeature.md || echo \"MISSING: feature.md\"\ntest -f docs\u002Fdefine\u002Ffeatures\u002F{slug}\u002Fmvp.md || echo \"MISSING: mvp.md\"\n\n# Rule\ntest -f docs\u002Frules\u002F{category}\u002F{slug}\u002Frule.md || echo \"MISSING: rule.md\"\ntest -f docs\u002Frules\u002F{category}\u002F{slug}\u002F.enforced_by || echo \"MISSING: .enforced_by\"\n```\n\n### Check Required Sections\n\n```bash\n# For any markdown file, check for required headings\nfile=$1\nrequired=(\"## Summary\" \"## Objectives\" \"## Acceptance Criteria\")\n\nfor section in \"${required[@]}\"; do\n  grep -q \"$section\" \"$file\" || echo \"MISSING: $section in $file\"\ndone\n```\n\n---\n\n## Common Creation Patterns\n\n### New Feature Flow\n\n1. Create feature definition\n2. Create mvp.md defining scope\n3. Create phase_0.md for initial work\n4. Create tasks for phase_0\n\n```bash\n# 1. Feature folder\nmkdir -p docs\u002Fdefine\u002Ffeatures\u002Fsearch\n\n# 2. Feature definition\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Ffeature.md \u003C\u003C 'EOF'\n# Feature: Global Search\n\n## Summary\nFuzzy search across all content types.\nEOF\n\n# 3. MVP scope\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Fmvp.md \u003C\u003C 'EOF'\n# MVP: Global Search\n\n## In MVP\n- Phase 0 only\n\n## Definition of Done\n- Search returns results in \u003C100ms\n- Fuzzy matching works\nEOF\n\n# 4. Phase 0\ncat > docs\u002Fdefine\u002Ffeatures\u002Fsearch\u002Fphase_0.md \u003C\u003C 'EOF'\n# Phase 0: Basic Search\n\n## Deliverables\n- MiniSearch integration\n- Global search component\nEOF\n\n# 5. Tasks\nmkdir -p docs\u002Ftodo\u002Fpending\u002Fsearch-minisearch-setup\n# ... create task\n```\n\n### New Rule Flow\n\n1. Identify pattern to standardize\n2. Create rule folder\n3. Write rule with examples\n4. Configure enforcement\n5. Announce to team\n\n```bash\n# 1. Rule folder\nmkdir -p docs\u002Frules\u002Fcode\u002Fasync-await\n\n# 2. Rule definition\ncat > docs\u002Frules\u002Fcode\u002Fasync-await\u002Frule.md \u003C\u003C 'EOF'\n# Rule: Prefer async\u002Fawait\n\n## Summary\nSHOULD use async\u002Fawait over .then() chains.\n\n## Rationale\nImproved readability and error handling.\n\n## The Rule\n...\nEOF\n\n# 3. Examples\ncat > docs\u002Frules\u002Fcode\u002Fasync-await\u002Fexamples.md \u003C\u003C 'EOF'\n# Examples\n...\nEOF\n\n# 4. Enforcement\necho \"eslint prefer-async-await\" > docs\u002Frules\u002Fcode\u002Fasync-await\u002F.enforced_by\n\n# 5. Configure ESLint\n# Edit .eslintrc.js\n```\n\n---\n\n## Signal Files Quick Reference\n\n| Signal         | Used For    | Content                  |\n| -------------- | ----------- | ------------------------ |\n| `.version`     | All         | JSON schema version      |\n| `.priority`    | Tasks       | critical\u002Fhigh\u002Fmedium\u002Flow |\n| `.enforced_by` | Rules       | List of tools            |\n| `.status`      | Definitions | draft\u002Freview\u002Fapproved    |\n| `.created_at`  | All         | ISO timestamp            |\n| `.created_by`  | All         | Author name              |\n\n---\n\n## Creation Checklist\n\nBefore finalizing any created document:\n\n- [ ] Folder uses slug format\n- [ ] Primary file exists (task.md, feature.md, etc.)\n- [ ] .version signal added\n- [ ] Required sections present\n- [ ] No TODO placeholders remain\n- [ ] Links are valid\n- [ ] Spelling\u002Fgrammar checked\n- [ ] Related documents cross-referenced\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Feduardou24\u002Fogt-docs-create",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-create",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-create",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill ogt-docs-create","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Feduardou24\u002Fogt-docs-create\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]