Menu
Scan conductor/ directory for project direction, workflows, and task planning when present
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Systematic testing of code variations, edge cases, boundary conditions, and alternative implementations. This skill provides methodologies and tools for exhaustive testing including input permutation, code path analysis, mutation testing, and implementation alternatives. Use when ensuring code robustness through comprehensive test coverage or when exploring edge cases and boundary conditions.
Specialized skill for MLX-based LLM fine-tuning on Apple Silicon. This skill should be used when working with LoRA fine-tuning, model conversion from HuggingFace to MLX format, adapter management, hyperparameter tuning, memory optimization, and benchmarking on M1/M2/M3/M4 chips.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
n8n workflow development patterns, testing, validation, and best practices for building composable webhook workflows
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
| name | use-conductor |
| description | Scan conductor/ directory for project direction, workflows, and task planning when present |
Scan the conductor/ directory at project root for structured project management files that provide direction, workflows,
and task planning context.
Use this skill when:
The conductor system uses this structure:
conductor/
├── product.md # Product vision and purpose
├── product-guidelines.md # Standards and conventions
├── tech-stack.md # Technology decisions
├── workflow.md # Task execution methodology
├── tracks.md # Index of active work tracks
├── setup_state.json # Setup progress state
├── code_styleguides/ # Language-specific style guides
│ ├── general.md
│ └── python.md
└── tracks/ # Detailed track plans
└── <track_name>/
├── spec.md # Track specification
├── plan.md # Task checklist with progress
└── metadata.json # Track metadata
| File | Purpose |
|---|---|
product.md | Product vision, target audience, core features |
product-guidelines.md | Naming conventions, quality standards, documentation rules |
tech-stack.md | Approved technologies and libraries |
workflow.md | TDD methodology, task workflow, commit guidelines |
tracks.md | High-level index of all work tracks |
tracks/<name>/plan.md | Detailed task checklist with [ ], [~], [x] status |
tracks/<name>/spec.md | Goals, scope, and success criteria for the track |
conductor/ directory exists at project rootproduct.md for visionproduct-guidelines.md for standardstracks.md for active work[~]), read the track's plan.md to find current tasksworkflow.mdIn plan.md files:
[ ] - Task not started[~] - Task in progress[x] - Task completed (may include commit SHA)When conductor files are present:
plan.md[~] when starting, [x] when doneproduct-guidelines.md and style guidesspec.md for what's in/out of scopeBefore starting work on a project:
User: "What should I work on next?"
Claude: [Checks for conductor/ directory]
[Reads tracks.md to find active track]
[Reads tracks/<active>/plan.md to find next [ ] task]
"According to the conductor plan, the next task is..."