Workflow

The problem

Starting projects with different coding agents kept producing the same missing context, inconsistent setup, and delivery questions. I wanted one repeatable starting point that still leaves room for the project itself.

What I built

• Created separate workflow-init and site-init paths for product applications and marketing sites.
• Packaged reusable context documents, feature and cleanup skills, and delivery guidance for multiple coding agents.
• Added idempotent setup behavior so an existing project can be inventoried or refreshed without blindly replacing its files.

Key decisions

• Use the open agent-skills standard where possible instead of tying the package to one coding agent.
• Keep project strategy and delivery context in normal Markdown files that remain useful without an agent.
• Separate marketing-site setup from application feature workflows because they need different levels of process.

How I check the work

• Install the package into a temporary project and inspect the generated files.
• Run the product and site setup paths independently.
• Use npm package dry runs and local install checks before publishing package changes.