AlessioScarfone
- 27 skills
- 0 followers
- 6 hours ago last updated
- ▌ Caveman · alessioscarfoneUltra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
- ▌ Skill Creator · alessioscarfone bundleAuthors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
- ▌ Pr Description · alessioscarfoneGenerate pull/merge request titles and descriptions from diffs and context. Use when creating a PR, writing PR description, drafting merge request, or summarizing changes for review.
- ▌ Create Agents Md · alessioscarfone bundleGenerate an AGENTS.md file for a repository. Use when user asks to create AGENTS.md files, analyze codebase for AI agent documentation, set up AI-friendly project documentation, or generate context files for AI coding assistants. Triggers on "create AGENTS.md", "generate agents", "analyze codebase for AI", "AI documentation setup", "hierarchical agents".
- ▌ Create UX Prototype · alessioscarfone bundleFacilitate UX design sessions with structured brainstorming, design decision workshops, UX specification writing, and standalone HTML/CSS prototyping. Use when user asks to design a UI, create a UX prototype, brainstorm design decisions, review a design, build an HTML mockup, create a wireframe, or mentions "UX", "prototype", "wireframe", "design decisions", "UI design", "mockup".
- ▌ Sdd UX · alessioscarfoneCreate or update the shared UX design document — define user flows, create wireframe mockups, document interaction patterns, specify navigation and component inventory, and produce an HTML/CSS prototype. Use when defining UX flows, wireframes, or interaction design for the product. Do not use for architecture decisions, product requirements, or feature implementation.
- ▌ Sdd Prd · alessioscarfoneCreate or update the shared PRD — discover product vision, map user journeys, define functional requirements, and write success criteria and NFRs. Use when defining product requirements, revising the product vision, or updating the PRD. Do not use for architecture decisions, UX design, or implementing features.
- ▌ Sdd Arch · alessioscarfoneCreate or update the shared architecture document — select tech stack, define API patterns, establish naming conventions, map project structure, and record architectural decisions with rationale. Use when designing system architecture, making technical decisions, or updating the architecture doc. Do not use for implementing features, writing PRDs, or designing UX.
- ▌ Sdd Help · alessioscarfone bundleLearn about the SDD process — get a quick overview, deep dives into each artifact type (PRD, architecture, UX, changes, specs), team roles, and available skill commands. Use when onboarding to SDD, looking up how a skill works, or asking about roles and process stages. Do not use for creating or editing SDD documents or implementing changes.
- ▌ Sdd Init · alessioscarfoneSet up SDD on an existing project — inspects the codebase, interviews the user, and generates prd.md, architecture.md, ux.md (if a UI exists), and sdd-tracker.yml. Use when adopting SDD on legacy code or an existing codebase that has no SDD artifacts yet. Do not use for new (greenfield) projects or for updating SDD documents that already exist.
- ▌ Typeset Free · alessioscarfoneGenerate a self-contained HTML document styled entirely from a DESIGN.md file — no pre-built templates. Reads any DESIGN.md (auto-discovered in project root, provided by path, or pasted inline) and produces a pixel-faithful one-pager, resume, letter, long-doc, or slide deck in HTML + PDF. Supports Latin-script languages only (English, Italian, Spanish, French, German, Portuguese, Dutch, Polish, etc.). Does not support Chinese, Japanese, Korean, or other CJK scripts — use Kami for those. Triggers on "typeset this", "design a document", "make a one-pager with my design system", "use my DESIGN.md", "generate a styled doc", "turn this into a PDF using my design". Do not use for coding tasks, CJK output, or when no design system is available.
- ▌ Sdd Verify · alessioscarfoneCompare code changes against spec requirements, validate task completion, and check design alignment before archiving a change. Use when a change has been implemented and you want to review my changes, check before merge, validate my implementation, or get a QA check before closing out. Do not use for implementing changes, creating artifacts, or archiving without prior verification.
- ▌ Typeset Print · alessioscarfoneTypeset professional print documents by overlaying a DESIGN.md design system onto bundled print templates. Reads any DESIGN.md (auto-discovered in project root, provided by path, or pasted inline), maps its tokens to template CSS variables, then fills the chosen template with the user's content. Best for structured print documents (resume, one-pager, letter, long-doc, slides, equity report, changelog) where predictable layout matters more than pixel-perfect design-system fidelity. Supports Latin-script languages only (English, Italian, Spanish, French, German, Portuguese, Dutch, etc.). Does not support Chinese, Japanese, or Korean. Triggers on "typeset this document", "use a print template", "apply my DESIGN.md to a document template", "generate a styled document". Do not use for CJK output or dark/screen-only design systems (use typeset-free instead).
- ▌ Sdd Archive · alessioscarfoneClose out a completed SDD change — syncs delta specs to main specs, moves the change directory to the archive folder, and updates the tracker status to archived. Use when a change is verified and ready to finish, close ticket, mark complete, or close out. Do not use for changes still in progress, unverified, or not yet implemented.
- ▌ Sdd Explore · alessioscarfoneOpen-ended thinking partner mode — investigate problems, map codebase architecture, compare options, visualize tradeoffs, and capture decisions in SDD artifacts. Use when brainstorming solutions, evaluating options, or researching before committing to a design. Do not use for generating deliverable documents or implementing code.
- ▌ Sdd Propose · alessioscarfoneScope a new change end-to-end — writes a proposal, design doc, capability specs, and task list, then updates the shared PRD, UX, and architecture as needed. Use when scoping new product changes, creating a proposal with spec, design, and tasks in one workflow. Do not use for implementing already-proposed changes or updating a single shared document in isolation.
- ▌ Sdd Tracker · alessioscarfoneInternal skill — auto-invoked by sdd-prd, sdd-arch, sdd-ux, sdd-propose, sdd-implement, sdd-verify, and sdd-archive to create and maintain the SDD workflow tracker file (sdd-tracker.yml). Covers file initialization, shared artifact tracking, change status transitions (proposed → in-progress → done → verified → archived), changelog entries, and project.lastUpdate housekeeping. Invoke after producing or modifying any SDD artifact. Do not invoke directly — use the relevant SDD workflow skills instead.
- ▌ Code Review · alessioscarfone bundleRun a multi-perspective code review that spawns parallel reviewer agents focused on different quality dimensions — simplicity/DRY, bugs/correctness, and project conventions — then consolidates findings into a single prioritized report. Use when the user asks to review code, check for bugs, audit recent changes, review a branch or PR, inspect code quality, or wants a second pair of eyes on their work. Also triggers on "review my changes", "anything wrong with this code", "check before I push", "sanity check", or "code audit". Do not use for implementing features, writing new code, or refactoring — those have their own workflows.
- ▌ Feature Dev · alessioscarfone bundleGuides end-to-end feature implementation — explores the codebase, resolves ambiguities via clarifying questions, compares architecture approaches, then implements and reviews the result. Use when adding a new feature, implementing a user story, building a new endpoint, or planning how to build something in an existing codebase. Do not use for bug fixes, refactoring existing code, quick one-off edits, or tasks that only need a spec or plan without implementation.
- ▌ Sdd Task Dag · alessioscarfone bundleGenerates a conservative task-dependency DAG (task-dag.md) from tasks.md using codebase inspection. Groups tasks into conflict-free execution waves where tasks in the same wave touch no shared files. Use when preparing for parallel implementation, before running the sdd-dev-orchestrator, or when asked to "build the task DAG", "plan parallel execution", or "generate task-dag". Do not use for general task listing, project planning outside SDD, or implementation.
- ▌ Mini Sdd Plan · alessioscarfoneGenerate or update the implementation plan for an existing spec — read spec.yaml and break it into an ordered, testable task checklist. Use when creating a plan from a spec, generating tasks, planning how to implement a feature, or refreshing a plan after the spec changed. Do not use for writing the spec itself (use mini-sdd-spec) or implementing code (use mini-sdd-implement).
- ▌ Mini Sdd Spec · alessioscarfoneCreate or update a feature spec — define functional requirements and cross-cutting constraints for a single feature in a structured spec.yaml. Use when defining a new feature, capturing a requirement, writing a user story, drafting a spec, or refining an existing spec. Do not use for generating the implementation plan (use mini-sdd-plan) or implementing code.
- ▌ Sdd Implement · alessioscarfoneWrite code, modify files, run tests, and mark tasks done to implement a change from its spec. Use when executing development tasks defined in a change spec, building a feature, coding this up, making the changes, or developing from a spec. Do not use for proposing new changes, designing architecture, or verifying completed work.
- ▌ Mini Sdd Guide · alessioscarfoneAutonomous knowledge base for the mini-SDD framework. Always read this skill when working on a mini-SDD project or when any message mentions mini-SDD, mini-sdd-context, mini-sdd-spec, mini-sdd-plan, mini-sdd-implement, mini-sdd-init-config, context.md, spec.yaml, plan.md, ARTIFACT_MAIN_FOLDER, SPECS_SUBFOLDER, hooks config, or spec-driven development. Do not use for creating context files, writing specs, planning, or implementing features — those have their own skills.
- ▌ Mini Sdd Context · alessioscarfone bundleCreate or update the project context document that captures product vision, architecture, and tech stack in a single file. Use when bootstrapping a new project with mini-SDD, onboarding AI agents to an existing codebase, or updating project context after completing a feature. Do not use for writing feature specs or implementing code.
- ▌ Mini Sdd Implement · alessioscarfone bundleImplement a feature from an existing spec file — write code, create tests, and update files to make a spec done. Use when executing development work defined in a spec, building or developing a feature, coding from a spec, or when asked to "implement the spec", "code this up", "develop the feature", or "follow the specification". Do not use for creating specs, updating project context, or proposing new features.
- ▌ Mini Sdd Init Config · alessioscarfone bundleScaffold or update the mini-sdd configuration file (mini-sdd.config.yml) that defines pre and post hooks for the context, spec, plan, and implement steps. Use when setting up hook customization, configuring hooks, adding new hooks, reviewing or editing hook settings, or when asked to "setup mini-sdd", "configure hooks", "edit the config yml", or "add a pre-hook". Do not use for implementing features, writing specs, or creating project context.