Kjell Tore Guttormsen ab504bdf8c refactor(marketplace): split cc-architect from ultraplan-local into its own plugin

Extract `/ultra-cc-architect-local` and `/ultra-skill-author-local` plus all 7
supporting agents, the `cc-architect-catalog` skill (13 files), the
`ngram-overlap.mjs` IP-hygiene script, and the skill-factory test fixtures
from `ultraplan-local` v2.4.0 into a new `ultra-cc-architect` plugin v0.1.0.

Why: ultraplan-local had drifted into containing two distinct domains — a
universal planning pipeline (brief → research → plan → execute) and a
Claude-Code-specific architecture phase. Keeping them together forced users
to inherit an unfinished CC-feature catalog (~11 seeds) when they only
wanted the planning pipeline, and locked the catalog and the pipeline into
the same release cadence. The architect was already optional and decoupled
at the code level — only one filesystem touchpoint remained
(auto-discovery of `architecture/overview.md`), which already handles
absence gracefully.

Plugin manifests:
- ultraplan-local: 2.4.0 → 3.0.0 (description + keywords updated)
- ultra-cc-architect: new at 0.1.0 (pre-release; catalog is thin, Fase 2/3
  of skill-factory unbuilt, decision-layer empty, fallback list still
  needed)

What stays in ultraplan-local: brief/research/plan/execute commands, all
19 planning agents, security hooks, plan auto-discovery of
`architecture/overview.md` (filesystem-level contract, not code-level).

What moved (28 files via git mv, R100 — full history preserved):
- 2 commands, 8 agents, 1 skill catalog (13 files), 2 scripts, 8 fixtures

Documentation updates: plugin CLAUDE.md and README.md for both plugins,
root README.md (added ultra-cc-architect section, updated ultraplan-local
section), root CLAUDE.md (added ultra-cc-architect to repo-struktur),
marketplace.json (registered ultra-cc-architect), ultraplan-local
CHANGELOG.md (v3.0.0 entry with migration guidance).

Test verification: ngram-overlap.test.mjs passes 23/23 from new location.

Memory updated: feedback_no_architect_until_v3.md now points at the new
plugin and reframes the threshold around catalog maturity rather than an
ultraplan-local milestone.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-04-30 17:18:47 +02:00

2 KiB

Raw Blame History

name	description	layer	cc_feature	source	concept	last_verified	ngram_overlap_score	review_status
output-styles-reference	CC output styles — configurable response shape, tone, length, and formatting baselines.	reference	output-styles	https://docs.claude.com/en/docs/claude-code/output-styles	output-style-config	2026-04-18	null	approved

Output Styles — Reference

Output styles let a user or plugin shape how Claude Code responds: length defaults, formatting preferences, tone, verbosity. They apply across the session rather than needing to be re-stated per prompt.

Where they live

Built-in styles — shipped with the CLI.
Custom styles — directory with a manifest describing the style.
Selection — the user sets an active style via settings or a /style command. The style is injected into Claude's system context.

What a style can control

Default response length baseline ("keep responses ≤ 100 words unless detail is required").
Formatting rules (markdown vs plain, code-block conventions).
Tone ("terse", "pedagogical", "adversarial").
Domain voice (Norwegian for dialog, English for code — a project convention encoded as a style).

What a style cannot control

Tool permissions (that is allowed-tools / settings.json).
Hooks (those are harness-level).
Agent system prompts (those come from agent definitions).

When to use a custom style

The project has a persistent communication convention that should hold across every session (e.g., "never use emojis").
Multiple users share the project and want consistent output.
A skill's prompts would otherwise have to restate formatting rules each time.

When not to

For per-task formatting needs — use the prompt instead.
For rules that must hold against prompt injection — use hooks.

Practical shape

A minimal custom style is a markdown or plain-text block listing the conventions. Claude treats it as top-of-system guidance. Keep it short: long styles crowd out the task.

2 KiB Raw Blame History