add-feature
Extends Syncpack functionality through new commands and validation rules.
Install
mkdir -p .claude/skills/add-feature && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3346" && unzip -o skill.zip -d .claude/skills/add-feature && rm skill.zipInstalls to .claude/skills/add-feature
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Add new features to Syncpack including commands and validation logic. Use when implementing new CLI commands, adding InstanceState variants, or extending version group behaviour.Key capabilities
- →Register new CLI commands
- →Define InstanceState validation variants
- →Extend version group behavior
- →Implement command dispatch logic
How it works
Developers follow a 3-phase pattern (Create Context, Inspect Context, Run Command) to register new features across CLI, main, and command modules.
Inputs & outputs
When to use add-feature
- →Implementing a new CLI command for Syncpack
- →Adding a validation rule for version groups
- →Extending InstanceState functionality
About this skill
Add Feature
Guide for adding new functionality to Syncpack.
Quick Decision
What are you adding?
- New CLI command (lint, fix, format, etc.) → See adding-command.md
- New validation logic (InstanceState variant) → See adding-instance-state.md
- Both → Start with instance state, then add command
Prerequisites
Before adding any feature:
- Understand the 3-phase pattern: Create Context → Inspect Context → Run Command
- Know which phase your feature affects
- Check if similar code exists (use
ast-grep -p 'PATTERN' src/)
Feature Types
Commands
Commands are user-facing operations (syncpack lint, syncpack fix, etc.).
When to create a new command:
- New user-facing operation that doesn't fit existing commands
- Different output format or behaviour needed
Registration points (all three required):
src/cli.rs- Add toSubcommandenumsrc/main.rs- Add match arm for dispatchsrc/commands/*.rs- Implementpub fn run(ctx: Context) -> i32
→ Full guide: adding-command.md
Instance States
InstanceState variants describe validation results (valid, fixable, unfixable, suspect).
When to add a new state:
- New validation rule needed
- New type of error/warning to report
- New auto-fix capability
Location: src/instance_state.rs + src/visit_packages/*.rs
→ Full guide: adding-instance-state.md
Common Workflow
- Write failing test using TestBuilder
- Implement minimal code to pass
- Run
cargo clippyand fix warnings - Refactor if needed
- Update documentation
Checklist
Before submitting:
- Tests pass (
just test) - Zero clippy warnings
- Follows existing patterns
- Registered in all required places (for commands)
- Uses TDD approach
When not to use it
- →Modifying existing commands without following the 3-phase pattern
Prerequisites
Limitations
- →Requires registration in three distinct locations for new commands
- →Must pass all clippy warnings
How it compares
It mandates a strict TDD approach and specific registration points in Rust source files, ensuring consistency with existing Syncpack architecture.
Compared to similar skills
add-feature side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| add-feature (this skill) | 1 | 4mo | No flags | Intermediate |
| godot | 1,044 | 5mo | Review | Intermediate |
| software-architecture | 333 | 6mo | No flags | Intermediate |
| drizzle | 238 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by JamieMason
View all by JamieMason →You might also like
godot
bfollington
This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
drizzle
lobehub
Drizzle ORM schema and database guide. Use when working with database schemas (src/database/schemas/*), defining tables, creating migrations, or database model code. Triggers on Drizzle schema definition, database migrations, or ORM usage questions.
screenshot-to-code
OneWave-AI
Convert UI screenshots into working HTML/CSS/React/Vue code. Detects design patterns, components, and generates responsive layouts. Use this when users provide screenshots of websites, apps, or UI designs and want code implementation.
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
codex
Lucklyric
Invoke Codex CLI for complex coding tasks requiring high reasoning capabilities. This skill should be invoked when users explicitly mention "Codex", request complex implementation challenges, advanced reasoning, or need high-reasoning model assistance. Automatically triggers on codex-related requests and supports session continuation for iterative development.