Apply one optional StyleSeed aesthetic profile without changing the selected output grammar, product job, or core design judgment.
Scanned 8/31/2026
Install to Claude Code
npx -y skills add bitjaru/styleseed --skill ss-restyle --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ss Restyle?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bitjaru-ss-restyle)More formats (shields.io, HTML) on the badges page.
---
name: ss-restyle
description: Apply one optional StyleSeed aesthetic profile without changing the selected output grammar, product job, or core design judgment.
argument-hint: "<profile> — swiss | editorial | technical | warm-dtc | minimal-mono | brutalist-lite | none"
allowed-tools: Read, Write, Edit, Grep, Glob, Bash
---
# Apply an aesthetic profile
## Registry-first artifact boundary
When `.styleseed/project.json` and `.styleseed/artifacts/index.json` exist, resolve the requested artifact ID first, then read only `.styleseed/bundles/<artifact-id>.md` and `.styleseed/manifests/<artifact-id>.json`. Never fall back to the global legacy bundle for a registry project. Legacy projects may use `.styleseed/effective-rules.md` only when no registry exists.
Read `PRODUCT-PRINCIPLES.md`, `RULESETS.md`, `PRESETS.md`, and `STYLESEED.md`. Profiles are
coordinated visual axes; output grammars organize attention, information, and action. Keep them
separate.
## Workflow
1. Validate that the lock has one output grammar. If not, run `/ss-setup` first.
2. Select exactly one profile from `PRESETS.md`, or `none`. Never stack profiles.
3. Apply its coordinated radius, density, type, palette temperature, elevation, motion,
composition accent, and signature move **inside the output grammar's allowed ranges**.
4. Preserve deliberate brand values and required fonts when compatible. If incompatible, the
output grammar and core invariants win; explain the conflict.
5. Update `Aesthetic profile` and affected bounded values in `STYLESEED.md`. Do not rewrite the
output grammar or a reference-compiled rule set.
6. Run `/ss-score` to ≥80 and `/ss-verify` if renderable. Report the complete effective rule set,
not just the profile name.
## Rules
- A profile is optional appearance coordination, not a design-method exemption.
- `technical` profile does not turn a commerce page into an observability console.
- `editorial` profile does not justify unreadable serif body in a transaction workflow.
- `brutalist-lite` still requires coherent states, contrast, and one border language.
- Use `/ss-dial` for one-axis changes and `/ss-reference` for a new evidence-derived language.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.