development-workflows

Enforces code quality gates and config-first conventions for development workflows.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill development-workflows-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-workflows
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/development-workflows
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill development-workflows-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent development practices lead to unverified code being marked complete and wasted effort on redundant system discovery calls. This Skill codifies mandatory quality gates and efficiency rules so agents and developers follow the same conventions every time. ## Core Features & Use Cases - Mandatory Quality Gates: Requires linting, type-checking, and auto-formatting to pass before any code is considered complete. - Config-First Principle: Reads preferences from .agents/preferences.yaml or project config instead of running dynamic discovery commands, cutting latency from ~500-1000ms to ~100ms. - Function Call Optimization: Instructs agents to execute identification functions once per task and reuse the stored results. - Use Case: An AI coding agent starting a task reads the project config once, remembers the environment details, and runs lint and typecheck before declaring the work finished. ## Quick Start Apply the development-workflows conventions so that linting, type-checking, and config-first discovery are enforced before marking this task complete.

Frequently Asked Questions about development-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce linting and type-checking before completing code changes?

Run linting and type-checking as mandatory gates before considering any code complete, and auto-format before staging. All quality checks must pass before the work is declared finished.

What is the config-first principle for agent workflows?

Config-first means reading preferences from .agents/preferences.yaml or project config instead of running dynamic discovery commands. If config exists, ignore discovery entirely; only fall back to system commands when config is missing.

Why is reading a config file faster than dynamic discovery?

A single file read takes roughly 100ms, while running and parsing a system discovery command takes 500-1000ms. Config reads also avoid command parsing failures and reduce token usage from multiple tool calls.

How do I avoid repeated function calls in an agent task?

Execute identification functions once at task start, store the results, and reuse them throughout the task. Document this explicitly by stating the value is identified once and remembered for the task.

When should dynamic discovery be used instead of config files?

Dynamic discovery is only a fallback when no config file exists. If .agents/preferences.yaml or project config is present, discovery commands should never be run alongside it.