@slycode/slycode 0.1.19 → 0.2.0

package/dist/store/skills/claude-code-docs-maintainer/SKILL.md

@@ -1,168 +0,0 @@
----
-name: claude-code-docs-maintainer
-description: >
-  Maintains and updates the Claude Code documentation in the SlyCode repository.
-  Triggers when asked to update Claude Code docs, check for new versions,
-  or research recent Claude Code changes. Knows the documentation structure
-  and update procedures.
-version: 1.0.1
-updated: 2026-02-22
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Glob
-  - Grep
-  - WebSearch
-  - WebFetch
-  - Bash
----
-
-# Claude Code Documentation Maintainer
-
-This skill guides the maintenance and updating of Claude Code documentation stored in the SlyCode repository.
-
-## Documentation Location
-
-All Claude Code documentation is stored in:
-```
-documentation/reference/claude-code/
-```
-
-## Documentation Structure
-
-```
-claude-code/
-├── FUNCTIONALITY-MANIFEST.md    # Master reference document
-├── VERSION-MANIFEST.md          # Version tracking and update log
-└── features/                    # Deep-dive feature docs
-    ├── SKILLS.md
-    ├── HOOKS.md
-    ├── SUBAGENTS.md
-    ├── MCP.md
-    └── PLUGINS.md
-```
-
-## Update Procedure
-
-When asked to update the documentation, follow these steps:
-
-### 1. Check Current Version
-
-```bash
-claude --version
-```
-
-Compare against version in VERSION-MANIFEST.md.
-
-### 2. Research Changes
-
-Use WebSearch to find recent changes:
-- Search: "Claude Code [version] release notes features"
-- Search: "Claude Code changelog [date range]"
-
-Check official sources:
-- https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
-- https://github.com/anthropics/claude-code/releases
-- https://code.claude.com/docs/en/
-
-### 3. Identify New Features
-
-Look for:
-- New tools or commands
-- Setting changes
-- CLI flag additions
-- Plugin/MCP updates
-- Breaking changes
-- Deprecations
-
-### 4. Update Documentation Files
-
-For each change:
-
-1. **FUNCTIONALITY-MANIFEST.md** - Update relevant sections
-2. **VERSION-MANIFEST.md** - Add version entry and update tracking
-3. **features/*.md** - Update specific feature docs if affected
-
-### 5. Update Version Info
-
-In VERSION-MANIFEST.md:
-- Update "Installed Version"
-- Update "Documentation Date"
-- Add entry to "Update Log"
-- Record new features in "Version History"
-
-### 6. Verify Accuracy
-
-Cross-reference against:
-- Official documentation
-- Community feedback
-- Actual behavior testing
-
-## Adding New Feature Documentation
-
-When a major new feature is added:
-
-1. Create new file in `features/` directory
-2. Follow existing format (see SKILLS.md as template)
-3. Include:
-   - Overview section
-   - Configuration details
-   - Best practices
-   - Common pitfalls
-   - Examples
-4. Add reference in FUNCTIONALITY-MANIFEST.md
-5. Update VERSION-MANIFEST.md feature matrix
-
-## Research Sources
-
-### Official Sources (Highest Priority)
-- https://code.claude.com/docs/en/
-- https://github.com/anthropics/claude-code
-- https://anthropic.com/engineering/claude-code-best-practices
-
-### Community Sources (Verify Accuracy)
-- https://claudelog.com/claude-code-changelog/
-- https://claudefa.st/blog/guide/changelog
-- Medium articles from trusted authors
-- Hacker News discussions
-
-### Plugin Information
-- Official marketplace: browse via `/plugin discover`
-- https://github.com/ccplugins/awesome-claude-code-plugins
-- https://github.com/Piebald-AI/claude-code-lsps
-
-## Quality Standards
-
-All documentation must be:
-- **Accurate** - Verified against actual behavior
-- **Current** - Reflects latest version
-- **Dense** - Information-rich, minimal fluff
-- **Practical** - Includes examples and use cases
-- **Actionable** - Clear guidance on when/how to use
-
-## Document Versions
-
-When updating any document, always:
-1. Update the version number at the bottom
-2. Update the "Last Updated" date
-3. Use `date +%Y-%m-%d` for accurate date
-
-## Feature Audit Process
-
-To prevent missing features (like status line was initially missed), use the audit checklist:
-
-1. Read `FEATURE-AUDIT-CHECKLIST.md`
-2. Run through each category systematically
-3. Check official docs index for unlisted pages
-4. Review changelog for recent additions
-5. Verify slash commands via `/` + Tab
-6. Check settings via `/config`
-7. Update checklist with findings
-
-## Frequency
-
-Recommended update schedule:
-- **Weekly**: Check changelog for new releases
-- **Monthly**: Full feature audit using checklist
-- **On Release**: Update within 48 hours of major release

package/dist/store/skills/create-command/SKILL.md

@@ -1,92 +0,0 @@
----
-name: create-command
-version: 1.0.1
-updated: 2026-02-22
-allowed-tools: Write, Read, Glob
-argument-hint: [command-name] [purpose/requirements description]
-description: Meta-command that creates structured slash commands with proper documentation
----
-
-# Slash Command Creator - Meta Command
-
-## Task
-Create a new slash command file at `.claude/commands/$1.md` based on the requirements: "$2 $3 $4 $5 $6 $7 $8 $9"
-
-## Analysis Phase
-
-First, I'll analyze the requirements to determine:
-1. What tools the new command will need
-2. What arguments it should accept
-3. What bash commands or file references it requires
-4. The optimal workflow structure
-
-## Command Generation
-
-Based on the command name "$1" and purpose described above, I'll generate a complete slash command with the following structure:
-
-### Generated Frontmatter
-I'll create appropriate frontmatter including:
-- `allowed-tools`: Minimal required permissions based on the command's purpose
-- `argument-hint`: Clear parameter hints if the command needs arguments
-- `description`: Concise description for `/help` listing
-- `model`: Specific model if beneficial for the task type
-
-### Generated Command Structure
-
-The new command will include these sections:
-
-#### 1. Summary
-A clear description of what the command accomplishes and when to use it
-
-#### 2. Variable Declarations
-- **Input Variables**: Parameters the command accepts (using $ARGUMENTS or $1, $2, etc.)
-- **Working Variables**: Internal variables the command will use during execution
-- **Output Variables**: Results or artifacts the command produces
-
-#### 3. Setup Tasks
-- Prerequisite checks using bash commands with `!` prefix
-- File discovery or validation
-- Environment preparation
-- Initial state capture
-
-#### 4. Workflow
-Step-by-step execution plan:
-- Data gathering phase
-- Processing/transformation phase  
-- Validation phase
-- Output generation phase
-
-Each step will include:
-- Clear description of the action
-- Required tool usage
-- Error handling considerations
-- Progress indicators where appropriate
-
-#### 5. Reporting Format
-How the command presents its results:
-- Summary statistics or metrics
-- Detailed findings organized by category
-- Action items or recommendations
-- File paths of generated artifacts
-- Success/failure indicators
-
-## Implementation
-
-Now I'll create the slash command file with all the above sections properly filled out based on your requirements.
-
-The generated command will be immediately usable and will follow best practices:
-- Minimal required permissions
-- Clear documentation
-- Structured workflow
-- Consistent output format
-- Error handling
-
-## Post-Creation Summary
-
-After creating the command, I'll provide:
-1. **Location**: Where the command was created
-2. **Usage**: How to invoke it with examples
-3. **Capabilities**: What it can do
-4. **Testing**: Quick verification steps
-
-Let me now generate your slash command...

package/dist/store/skills/doc-discovery/SKILL.md

@@ -1,18 +0,0 @@
----
-name: doc-discovery
-version: 1.0.1
-updated: 2026-02-22
-allowed-tools: Task
-argument-hint: [optional date to check from]
-description: Run documentation discovery phase without modifications
-model: sonnet
----
-
-# Documentation Discovery Analysis
-
-Run a fresh documentation discovery analysis using the doc-updater agent without making any modifications. The doc-updater agent will:
-1. Create a new agentic discovery document
-2. Analyze all changes since last documentation update
-3. Provide a complete report of needed documentation updates
-
-This is explicitly a discovery-only run - no documentation will be modified

package/dist/store/skills/doc-update/SKILL.md

@@ -1,15 +0,0 @@
----
-name: doc-update
-version: 1.0.1
-updated: 2026-02-22
-allowed-tools: Task
-argument-hint: [agentic-discovery-file]
-description: Execute documentation updates based on discovery file
-model: sonnet
----
-
-# Documentation Update Execution
-
-Execute documentation updates with the doc-updater agent based on the provided agentic discovery file @$1. If no file is provided, will use the most recently generated discovery document from doc-discovery command.
-
-Please implement the documented changes based on the discovery analysis. Update all documentation as specified in the discovery file.

package/dist/store/skills/dummy/SKILL.md

@@ -1,22 +0,0 @@
----
-name: dummy
-version: 1.0.1
-updated: 2026-02-26
-description: "Inert test skill for validating frontmatter parsing, tool restrictions, and cross-provider conversion"
-provider: claude
-allowed-tools: [Bash, Grep, Glob, Read]
----
-
-# Dummy Skill
-
-A deliberately inert skill that carries realistic frontmatter (including tool restrictions) without performing any actual work. Useful for validating that skill infrastructure — discovery, parsing, allowed-tools enforcement, and store conversion — handles a fully-dressed skill correctly.
-
-## When to Invoke
-
-Never. This skill has no operational behavior. If invoked, do nothing.
-
-## Notes
-
-- Safe to delete or archive at any time
-- Can be used as a minimal template when creating new skills
-- The `allowed-tools` field is present for testing purposes only