domains / families / agent-tooling / project-development

project-development

combined

This skill should be used for project-level decisions about LLM-powered systems: whether an LLM is the right primitive for the task at hand, the shape of a multi-stage batch or agent pipeline, token and cost estimation, choosing between single-agent and multi-agent at the project level, structured output design for downstream parsing, and structuring agent-assisted iteration. Use this when the unit of work is a whole project or a multi-stage pipeline. Route individual tool design to tool-design and individual skill-loading or context-budget tactics to context-optimization. This skill covers the principles for identifying tasks suited to LLM processing, designing effective project architectures, and iterating rapidly using agent-assisted development.

When to use

• Starting a new project that might benefit from LLM processing
• Evaluating whether a task is well-suited for agents versus traditional code
• Designing the architecture for an LLM-powered application
• Planning a batch processing pipeline with structured outputs
• Choosing between single-agent and multi-agent approaches
• Estimating costs and timelines for LLM-heavy projects

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The sickn33 copy is a broader, more operational version of the muratcankoylan copy. While they share the core 'Task-Model Fit' and 'Pipeline Architecture' concepts, the sickn33 copy includes specific implementation patterns like 'File System as State Machine' and 'Structured Output Design' that are absent from the muratcankoylan copy. Conversely, the muratcankoylan copy provides more granular routing logic for when to activate the skill versus other skills (tool-design, context-optimization). Combining them provides a complete methodology from high-level fit to low-level state management.