skills/local/cali-product-workflow/skills-workflow/cali-interface-brainstorm/SKILL.md
[Cali] Interface brainstorming skill. Use when generating interface proposals using the 5 archetypes method. Produces 5 independent proposals + hybrid recommendation. Part of cali-product-workflow but can be used standalone.
npx skillsauth add renatocaliari/agent-sync-public-skills cali-interface-brainstormInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tools: See
references/cli-tools/subagents.mdfor subagent patterns.
This skill executes the Interface Brainstorming phase. It can be run:
/skill:cali-interface-brainstorm — for quick interface exploration/skill:cali-product-workflowStep 1: Read the references/ files to guide the process:
| File | Covers | When to read |
|---|---|---|
| references/interface-context.md | Progressive Clarification, when to use, system equivalents | Before starting |
| references/interface-reconstruction.md | Context reconstruction, hidden job extraction | Before generating |
| references/interface-rules.md | Separation Rule, Forced Trade-Off Rule, output quality | Before generating |
| references/archetypes.md | 5 archetypes with descriptions | During generation |
| references/hybrid-recommendation.md | Hybrid recommendation strategy | Step 3 only |
Step 1: Generate 5 proposals in parallel (5 independent workers):
subagent({
tasks: [
{ agent: "worker", task: `Generate Proposal A (Archetype A — Conventional Standard) for [product context]. Full format per references/output-format.md.` },
{ agent: "worker", task: `Generate Proposal B (Archetype B — Interaction Paradigm Shift) for [product context]. Full format per references/output-format.md.` },
{ agent: "worker", task: `Generate Proposal C (Archetype C — Technological Vanguard) for [product context]. Full format per references/output-format.md.` },
{ agent: "worker", task: `Generate Proposal D (Archetype D — Radical Simplicity) for [product context]. Full format per references/output-format.md.` },
{ agent: "worker", task: `Generate Proposal E (Archetype E — Expert/Command-First) for [product context]. Full format per references/output-format.md.` },
],
concurrency: 5,
context: "fork"
})
.cali-product-workflow/{YYYY-MM-DD}/{_dir}/interfaces/interfaces_{v}.mdStep 2: Read references/output-format.md to format and concatenate all proposals.
CRITICAL: Hybrid is generated AFTER all 5 proposals are complete to avoid bias.
subagent({
agent: "worker",
task: `Read the 5 proposals (A-E) from .cali-product-workflow/{YYYY-MM-DD}/{_dir}/interfaces/interfaces_{v}.md.
Then generate a **Hybrid Proposal** that combines the strongest elements from 2 or more archetypes.
Follow references/hybrid-recommendation.md for the strategy.
Append to the interfaces file.`,
reads: [`.cali-product-workflow/{YYYY-MM-DD}/{_dir}/interfaces/interfaces_{v}.md`]
})
After all proposals + Hybrid, use references/cli-tools/plannotator.md for the Plannotator command format.
After visual review and approval, use Pattern 2 from ../../phases/ask-patterns.md to ask the user which proposal to follow.
Interface proposals are saved to:
.cali-product-workflow/{YYYY-MM-DD}/{_dir}/interfaces/interfaces_{v}.md
If a tool is unavailable, check:
../../../cali-product-workflow/references/cli-tools/
tools
Auto-initialize structured documentation for any project using lat.md (knowledge graph of markdown files with [[wiki links]], // @lat: code refs, and semantic search). Detects cali-product-workflow artifacts (spec-product.md, spec-tech.md, critiques) and uses them as seed material. Falls back to extracting business rules, architecture, and design decisions directly from the codebase. Use when a project lacks structured documentation or when lat.md/ is missing. After seeding, lat.md extension hooks keep documentation alive automatically.
testing
[Cali] Server security audit and hardening for private servers behind Tailscale. Use when: auditing server security, hardening SSH/firewall/Docker, checking for vulnerabilities, setting up fail2ban, reviewing port exposure, or responding to security alerts. Covers 6 layers: CloudFlare, UFW, Tailscale, SSH, Docker, Application. Triggers: "server security", "security audit", "harden server", "SSH hardening", "firewall rules", "UFW config", "fail2ban", "port security", "Docker security", "vulnerability check", "security review".
tools
Run supply chain security scans before installing packages or before releases. Triggers when: user installs a package (npm, pip, go get, brew), user asks to 'scan dependencies', 'check vulnerabilities', 'supply chain', 'security audit', 'run trivy', 'run socket', or before any release/deployment. Also triggers on mentions of: socket.dev, trivy, OSV-scanner, dotenvx, CVE, dependency audit. Covers all four tools with concrete commands.
tools
Create GitHub releases following project conventions. Triggers when: user says 'release', 'create release', 'push release', 'deploy to main', 'merge to main', user merges a PR to main, or when git push to main is detected. Also triggers on mentions of: gh release, semver, version bump, changelog, release-please. Covers: config-driven (read .release.yml and execute) and fallback (gh CLI) release flows, versioning rules, tag management, and the mandatory release-on-merge convention.