Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From claude-code-builder
Generates custom output style Markdown files for Claude Code with YAML frontmatter, instructions, behaviors, and principles. Saves to user (~/.claude/output-styles) or project (.claude/output-styles) directories with status output.
npx claudepluginhub alexanderop/claude-code-builder --plugin claude-code-builderHow this command is triggered — by the user, by Claude, or both
Slash command
/claude-code-builder:create-output-styleThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /create-output-style ## Purpose Generate custom output style files for Claude Code with proper structure and YAML frontmatter. ## Contract **Inputs:** - `$1` — STYLE_NAME (optional: name for the output style) - `--user` — Save to user-level directory (~/.claude/output-styles) - `--project` — Save to project-level directory (.claude/output-styles) - `--description "..."` — Brief description of the output style **Outputs:** `STATUS=<OK|FAIL> PATH=<path> SCOPE=<user|project>` ## Instructions 1. **Determine scope:** - If `--user` is provided: save to `~/.claude/output-styles/` - I...
/output-style-setupPrompts for project or user-level choice, then installs bkit output styles by copying 4 .md files to .claude/output-styles/ or ~/.claude/output-styles/. Lists files and suggests activation.
/styleApplies a design style (e.g., Material Design, Glassmorphism) from 263+ styles and generates implementation code in CSS, Tailwind, or styled-components format.
/f5-styleguideGenerates project style guides from learned patterns, shows sections, updates with new patterns, exports to Markdown/HTML/PDF/Confluence/Notion, and generates ESLint/Prettier/Stylelint configs.
/setupGenerates Korean CLAUDE.md template for project types like web app, API server, data pipeline, monorepo, or side project. Auto-detects tech stack from package.json/pom.xml/etc., fills TODOs, saves to ./CLAUDE.md.
/gen-claudeGenerate or enhance CLAUDE.md with project-specific guidance by analyzing codebase structure, languages, frameworks, linters, and build tools.
/SKILLGenerates CLAUDE.md project config file via interactive phases: detects environment and tools, collects developer profile, selects testing methodology and tech stack.
Share bugs, ideas, or general feedback.
Generate custom output style files for Claude Code with proper structure and YAML frontmatter.
Inputs:
$1 — STYLE_NAME (optional: name for the output style)--user — Save to user-level directory (~/.claude/output-styles)--project — Save to project-level directory (.claude/output-styles)--description "..." — Brief description of the output styleOutputs: STATUS=<OK|FAIL> PATH=<path> SCOPE=<user|project>
Determine scope:
--user is provided: save to ~/.claude/output-styles/--project is provided: save to .claude/output-styles/--user (user-level)Gather information:
--description, ask user what behavior they wantGenerate output style file using this template:
---
name: {{STYLE_NAME}}
description: {{DESCRIPTION}}
---
# {{STYLE_NAME}} Instructions
You are an interactive CLI tool that helps users with software engineering tasks.
{{CUSTOM_INSTRUCTIONS}}
## Specific Behaviors
{{SPECIFIC_BEHAVIORS}}
## Key Principles
- {{PRINCIPLE_1}}
- {{PRINCIPLE_2}}
- {{PRINCIPLE_3}}
Create the file:
STATUS=OK PATH=<full-path> SCOPE=<user|project>Inform user:
/output-style [style-name]Example 1: Basic usage
/create-output-style
# Claude will ask for style name and description interactively
Example 2: Full specification
/create-output-style "Teaching Assistant" --project --description "Explains concepts step by step with examples"
# STATUS=OK PATH=.claude/output-styles/teaching-assistant.md SCOPE=project
Example 3: User-level style
/create-output-style "Code Reviewer" --user --description "Focuses on thorough code review with best practices"
# STATUS=OK PATH=~/.claude/output-styles/code-reviewer.md SCOPE=user