From blueprint
This skill should be used when the user asks to "implement X", "add X feature", "create X", "refactor X", "fix X bug", "develop this story", "work on story", or needs guidance on development work - both ad-hoc tasks and story-based workflows with style guide compliance.
npx claudepluginhub urso/claudev --plugin blueprintThis skill uses the workspace's default tool permissions.
This skill provides guidance for both ad-hoc development tasks and structured story-based development with style guide support.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
This skill provides guidance for both ad-hoc development tasks and structured story-based development with style guide support.
Story-Based:
Ad-Hoc:
Rules in docs/ai/rules/ provide conventions and build instructions:
---
name: Go Style Guide
applies-to:
- go
tags:
- style
paths: [] # optional: glob patterns for path-based filtering
description: Go coding conventions and patterns.
---
Frontmatter fields:
name - display nameapplies-to - languages/technologies (use ["*"] for universal)tags - categories: style, build, testing, etc.paths - optional glob patterns for path-based filteringdescription - brief descriptionRules with applies-to: ["*"] apply to all code. Use tags to filter by category (style vs build).
To manually load style guides and build config:
/prime [tech...] [build|style]
Examples:
/prime - Load everything/prime go - Load go-related style guides + build.md/prime build - Only load build.md/prime style - Only load style guides/prime go rust - Load go and rust style guides + build.mdNote: For ad-hoc development tasks, the skill automatically loads context. Use this command when you want explicit control or to reload context.
To implement tasks from a story document:
/develop-story [story-file or story-name]
The command will:
For ad-hoc tasks without a story document, simply describe what you want:
"Implement user authentication"
"Add a delete button to the profile page"
"Refactor the API client to use async/await"
"Fix the memory leak in the event handler"
The skill will:
To fix build or lint errors:
/develop-fix [--story story-file]
The command will:
For automated end-to-end development:
/develop-loop [story-file]
This orchestrates:
/develop-story - Implement tasks (interactive)/develop-fix - Fix build errors/review-loop - Simplify, fix, and review-fix cycleStory-Based Development:
Ad-Hoc Development:
After completing tasks, update the story's developer logs:
These logs feed into future story creation and design updates.