From blueprint
This skill should be used when the user asks to "add to style guide", "update style guide", "create style guide", "add a convention", "learned from review", "add coding rule", or needs guidance on maintaining project style guides for consistent development. Also use after code reviews reveal patterns worth capturing.
npx claudepluginhub urso/claudev --plugin blueprintThis skill is limited to using the following tools:
Create and update style guides in `docs/ai/rules/` to capture conventions and learnings.
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.
Create and update style guides in docs/ai/rules/ to capture conventions and learnings.
${CLAUDE_PLUGIN_ROOT}/scripts/list-rules.sh$ARGUMENTS
Parse for:
common, go, kubernetes)!bash ${CLAUDE_PLUGIN_ROOT}/scripts/list-rules.sh "" "" style
Review the style rules listed in the pre-computed context above.
New rule file — create docs/ai/rules/<name>.md:
---
name: <Name> Style Guide
applies-to:
- <tech> # or ["*"] for universal
tags:
- style
paths: [] # optional: glob patterns for path-based filtering
description: <Brief description of what this guide covers>
---
# <Name> Style Guide
- [First rule]
Existing rule file — append the new rule to appropriate section, or create a section if needed.
For details on frontmatter fields, rule types, and integration with development, consult references/rule-structure.md.
Each rule should be:
Good: - Use structured logging with slog, not fmt.Printf
Bad: - When logging in Go, you should always use the structured logging package slog instead of using fmt.Printf because it provides better...
Add examples only when ambiguous:
- Wrap errors with context: `fmt.Errorf("failed to parse config: %w", err)`
Show what was added and confirm.
After code reviews reveal repeated feedback:
/style-update to add the ruleThis creates a feedback loop: reviews improve rules, rules improve code.
references/rule-structure.md — Rule file frontmatter fields, rule types, integration with development, symlink setup/style-update common always use structured logging
/style-update go prefer table-driven tests
/style-update kubernetes # interactive creation