ald-skills

Use PROACTIVELY to document new features, significant code changes, or when creating technical specifications for a feature not included in the original project technical specification. Specializes in creating comprehensive feature documentation for non-professional developers.

Write, read, and apply DESIGN.md files — Google Stitch's open AI-readable design-system format (YAML design tokens + Markdown rationale). Use when asked to "create a design.md", "extract a design system from [brand/PDF/site/screenshots]", "document this brand for AI tools", or when reverse-engineering a brand's visual identity into reusable tokens for an AI coding agent to apply consistently.

Builds complete bilingual email drafts from intent and audience. Use when the user asks to write, rewrite, localize, polish, or generate an email, campaign email, outreach message, customer update, follow-up, announcement, invite, sales email, internal note, or lifecycle email and wants clear subject lines, preheaders, body copy, CTAs, variants, or English and Spanish versions.

Provides the single source of truth for brand guidelines, design tokens, technology choices, and voice/tone. Use when applying brand colors, defining typography scale, configuring CSS custom properties, or writing copy that must match a specific brand voice. Triggers on: design tokens, brand colors, color palette, typography, font family, voice & tone, CSS variables, brand consistency, design system initialization.

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Upgrades existing UIs to premium quality by auditing generic AI patterns and applying high-end design standards. Use when UI looks flat, generic, or "AI-slop". Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. Source: github.com/leonxlnx/taste-skill (redesign-skill variant).

Correct protocol for crawling and researching external websites. Use this skill — always — before fetching any sub-page of a website you haven't visited before. Triggers on: "research this site", "check their website", "find out what X does", "scrape this competitor", "look at their features", "crawl this URL", "fetch pages from", "browse this site", "check what pages exist at", or any time you need information from multiple pages of the same domain. The rule is absolute: never guess or construct URL paths — always extract real hrefs from the homepage first.

Enriches vague, low-detail prompts into structured, agent-optimized XML before execution. INVOKE IMMEDIATELY — before any tool use or file reads — when you detect any of these signals: prompt under 10 words with no file path or error message; vague action verbs with no object ("fix the bug", "make it better", "clean this up", "refactor this", "optimize performance", "improve the UI", "add authentication", "add payments", "add notifications", "build the feature"); CLARIFIER_ADVISORY in your context window; user says "clarify", "help me describe this", "enrich this prompt", "structure my request". Also triggers on: "make this work", "it's broken", "it looks bad", "add X" with no further detail, "implement Y" with no constraints. Do NOT trigger on: prompts ending with ?, prompts containing error messages or stack traces, prompts with specific file paths, prompts already containing acceptance criteria or success metrics.

Expert Socratic discovery skill for exploring ideas, architecture decisions, and technical design before writing any code. Use this skill — proactively and always first — when requirements are vague, when the user is debating between technical approaches, when the problem is unclear, or when a design decision could have significant architectural consequences. Triggers on: "should we use X or Y", "help me think through", "I'm not sure how to approach this", "what's the best architecture for", "trade-offs between", "design before I code", "let's think through this", "I have an idea", "how should I structure", "help me design", "I want to build X but not sure how", "what approach would you recommend", "is this the right way to". Produces a validated design doc with 2-3 implementation options, trade-offs, and a recommendation. Always use before planning when the approach is not yet locked.

Profiles 5 competitors, identifies white space, and delivers a positioning recommendation — not a feature comparison table. Use this skill — proactively and without waiting to be asked — whenever entering a new market, before defining bets in product strategy, when pricing needs a competitive anchor, or when losing deals to a specific competitor. Also triggers for: "competitive analysis", "competitor research", "who are my competitors", "market landscape", "white space", "differentiation angle", "competitive positioning", "market entry risk", "losing to X", "pricing strategy", "threat assessment", "who owns this segment", "competitive brief", "how do we differentiate", "what are competitors doing". Produces a decision-ready competitive map: 5 competitor profiles, white space analysis, and a Where-to-Win recommendation with explicit areas to ignore.

Translates stakeholder feature requests into validated outcome statements before any work is committed. Use this skill — proactively and without waiting to be asked — whenever a stakeholder, exec, or customer arrives with a pre-packaged solution: "we need a dashboard", "add a Slack notification", "build an export feature", "create a report", "let's add a filter", "can we just add X". Also triggers for: "how do I push back on this request", "what outcome does this feature solve", "outcome vs output", "outcomes not features", "what are we really trying to achieve", "we're being a feature factory", "I need to reframe this as a problem", "the stakeholder is pushing a specific solution", "discovery before delivery", "assumption testing", "translate this request into an outcome", "ship outcomes not features". Runs the 'One Framework. Four Questions.' protocol (Liatti + Cagan + Torres): Behavior Change → Assumption Test → Cheapest Test → Success Metric. Produces an Outcome Brief with embedded AI prompts ready to pas

Reverse engineering de diseños Figma para generar especificaciones técnicas completas listas para implementar en código. Usar cuando el usuario comparte capturas, exports o descripciones de un diseño en Figma y quiere documentarlo técnicamente, extraer tokens de diseño, entender la estructura de layouts, o preparar una spec para que un desarrollador o Claude Code lo implemente. También usar cuando el usuario dice "reverse engineering del diseño", "documenta este Figma", "quiero implementar este diseño", "dame las propiedades CSS de este diseño", "convierte este diseño a código", o cuando comparte pantallazos de Figma (layers, propiedades, canvas). Activar también cuando el usuario quiere crear documentación técnica de un diseño existente antes de pasarlo a Claude Code.

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.

Creates atomic, TDD-focused implementation plans for features with approved designs. Use this skill — always AFTER brainstorming or when a design is already clear — when the user needs a step-by-step execution roadmap before coding starts. Triggers on: "write me a plan", "break this into tasks", "implementation steps for", "what order should I build", "atomic tasks", "TDD plan", "sprint breakdown", "create a plan for", "plan this feature", "step by step", "how do I implement", "what's the order of operations", "break this down for me". Also use when a user provides a spec and wants a concrete action plan with exact file paths and test commands. Produces an ordered task list where each task maps to one commit, with TDD steps (Red→Green→Refactor) and exact verification commands per task.

Expert product strategy advisor for Senior PMs. Use this skill — proactively and without waiting to be asked — whenever defining a product vision, setting quarterly OKRs, building a roadmap, choosing between competing bets, entering a new product area, or when stakeholders disagree on direction. Also triggers for: "what should we prioritize", "we need a north star", "how do we choose between X and Y", "roadmap conflict", "what are our bets this quarter", "strategy alignment", "choosing what NOT to build", "three bets with trade-offs", "stakeholder misalignment on direction", "product direction for next quarter", "OKR planning". Produces a decision-focused strategy doc: North Star metric, Opportunity Tree, three bets with explicit trade-offs (including do nothing), and a recommended bet with its key assumption.

Designs a precise value proposition using a 6-part JTBD template (Who / Why / What Before / How / What After / Alternatives). Use this skill — proactively and without waiting to be asked — whenever the product's positioning is unclear, a new customer segment is being targeted, or messaging is inconsistent across teams. Also triggers for: "value proposition", "value prop", "why would customers choose us", "positioning for new segment", "win/loss analysis shows customer confusion", "customers can't explain why they use us", "what's our differentiation", "elevator pitch", "why us over competitors", "competitive differentiation", "JTBD template", "what problem do we solve", "who is this product for". Produces one value prop per segment — not a tagline, a positioning decision — with a synthesized 1-2 sentence statement ready for a PRD problem statement, landing page headline, or sales deck.

Structured methodology for solving, writing, and presenting hiring case studies for Senior Product Manager and Technical PM roles. Use when resolving a case study, reviewing a case study response, or building a presentation prototype from a completed case study. Covers the full process from problem understanding to final delivery, including data analysis, written response, and interactive presentation.

Structured verbal communication framework for Senior PM and TPM interviews. Use when preparing for interviews, rehearsing answers, practicing English delivery under pressure, or when any interview question needs to be answered in a crisp, structured way. Covers SCQA/STAR scaffolding, answer templates by question type, pushback handling, English-under-pressure tactics, and post-interview debrief methodology. Trigger on any variant of "how do I answer this?", "rehearse with me", "how would you say this?", or "practice interview question".

Creates decision-focused PRDs and product specs — the kind that make explicit decisions, not document hopes. Make sure to use this skill whenever someone asks to write, review, draft, or improve any product document, including PRDs, feature specs, requirements docs, or product specifications. Trigger even when the user doesn't say "PRD" explicitly — phrases like "write a spec for X", "define requirements for Y", "what should my PRD include", "help me document this feature", or "my spec feels too vague" all apply. Do not attempt to write the PRD directly without consulting this skill. Produces 5-stage PRDs with behavior contracts (15-25 labeled examples for AI features), measurable success metrics with specific thresholds, precise rollout plans with percentages and ramp gates, and antipattern detection. Works for AI features, SaaS, mobile apps, and traditional software.

Maps the end-to-end customer experience from awareness to advocacy — touchpoints, emotions, friction points, and improvement opportunities per stage. Use when identifying drop-off points, improving onboarding, or understanding the full user lifecycle. Triggers on: customer journey, user journey, journey map, touchpoints, onboarding experience, funnel analysis, churn points, aha moment, drop-off, user lifecycle.

Drafts a Non-Disclosure Agreement covering parties, information types, duration, jurisdiction, and key clauses needing legal review. Use when starting work with contractors, freelancers, or partners. Triggers on: NDA, non-disclosure agreement, confidentiality agreement, contractor agreement, partnership NDA, freelancer agreement.

Identifies and designs growth loops (flywheels) for sustainable traction — evaluating 5 loop types: Viral, Usage, Collaboration, User-Generated, and Referral. Use when designing growth mechanisms or reducing reliance on paid acquisition. Triggers on: growth loop, flywheel, viral loop, referral program, product-led growth, PLG, user acquisition, growth strategy, retention loop, compounding growth.

Runs a structured pre-mortem on a PRD or launch plan, categorizing risks as Tigers, Paper Tigers, and Elephants, with launch-blocking action plans. Use before any significant product launch or execution milestone. Triggers on: pre-mortem, risk analysis, launch readiness, what could go wrong, launch risks, risk mitigation, launch blockers, stress-test plan.

Applies the right prioritization framework for the context — Opportunity Score, RICE, ICE, MoSCoW, or Kano — with formulas, scoring guidance, and when-to-use rationale. Use when ranking features or problems, comparing approaches, or preparing a prioritized backlog. Triggers on: prioritization, RICE, ICE, MoSCoW, Kano, backlog prioritization, feature ranking, opportunity score, prioritize features, what to build next.

Drafts a privacy policy covering data types collected, user rights, jurisdiction-specific requirements (GDPR, CCPA), and compliance considerations, with clauses marked for legal review. Use when launching an app or preparing for data compliance. Triggers on: privacy policy, GDPR, CCPA, data protection, data privacy, user data, cookie policy, compliance, data collection.

Expert product analytics advisor for Senior PMs. Use when defining success metrics for a PRD, designing an A/B experiment, setting up an analytics tracking plan, analyzing post-launch impact, or when data exists but there's no clarity on what to measure. Produces structured metrics frameworks that connect to product decisions, not dashboards.

Facilitates a sprint retrospective using Start/Stop/Continue, 4Ls, or Sailboat format, producing 2-3 prioritized action items with owners and deadlines. Use after a sprint or milestone to drive continuous improvement. Triggers on: retrospective, retro, sprint review, what went well, lessons learned, team improvement, action items, start stop continue, post-mortem, sprint reflection.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Builds a Power × Interest stakeholder map and generates a communication plan per quadrant. Use when managing a complex launch, aligning cross-functional teams, or preparing stakeholder engagement strategy. Triggers on: stakeholder management, stakeholder map, stakeholder alignment, communication plan, power interest grid, cross-functional alignment, executive alignment, managing up.

Expert user research and discovery advisor. Use before writing a PRD, when validating product assumptions, when metrics signal a problem but not the "why", when exploring a new user segment or job-to-be-done, or when preparing for stakeholder interviews. Produces structured discovery synthesis that feeds directly into product strategy and PRD writing.

Creates research-backed user personas with JTBD, pain points, gains, and unexpected behavioral insights. Use when building personas from survey or interview data, or segmenting users to inform product decisions. Triggers on: user persona, user profile, customer segment, jobs-to-be-done, JTBD, persona creation, user segmentation, target user, who are our users.

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when adding try/catch blocks, handling async errors, fixing silent failures, or designing fallback strategies. Triggers on: unhandled exception, error boundary, async error, retry logic, fallback, graceful degradation, API error response, catch block, error state.

Dispatch a code-reviewer subagent to catch issues before they cascade into production. Use before merging a PR, after completing a feature, or any time you want a second pass on code quality. Triggers on: "review my code", "check this PR", "code review", "review this", "before merge", "find bugs", "spot issues", pre-merge check.

Expert system for designing and architecting AI agent workflows based on proven Meta methodologies. Use when building AI agents, designing multi-agent systems, integrating tools into agent architectures, choosing between single vs. multi-agent setups, or translating a business problem into an agentic solution. Triggers on: "build an agent", "design agent workflow", "multi-agent system", "agent architecture", "how should I structure this agent". Covers 9-step building process, 8-layer architecture framework, MCP integration, and pitfall avoidance.

End-to-end content workflow from raw idea to published post across platforms. Chains writing-system (idea capture → draft → edit) with platform-specific publishing for X/Twitter, LinkedIn, blog, and newsletter. Use when you have a content idea and want to take it from capture to publication without skipping the edit pass. Triggers on: /publish, "write and publish this", "turn this into content", "draft a post about", "content workflow".

End-to-end workflow from approved PRD to public launch. Chains full-stack-build → changelog-generator → product-launch with explicit readiness gates. Use when a PRD is approved and you're ready to execute the complete build + launch cycle. Triggers on: /feature-launch, "build and launch this feature", "take this PRD to launch", "ship this feature". Prevents shipping without monitoring and launching without a changelog.

Multi-step workflow that takes a raw idea from validation through design to a complete PRD. Chains idea-validator → brainstorming → prd-writer with explicit gates between steps. Use when starting a new feature or side project from scratch. Triggers on: /idea, "validate this idea", "should I build this", "new feature idea", "take this idea to PRD". Prevents building without validating and prevents specifying without designing.

Designs REST and GraphQL APIs following production best practices for resource naming, error handling, versioning, authentication, and documentation. Use this skill when designing new API endpoints, reviewing API contracts, implementing GraphQL schemas, establishing API conventions for a project, or writing API documentation. Apply when creating any route in Next.js API routes or route handlers, any Supabase Edge Function, or any backend endpoint — even if it starts small, these patterns prevent painful rewrites later.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Guides end-to-end implementation of features in side projects, from design decision to deployment. Use when building a new feature from scratch, connecting frontend to backend, setting up a new side project architecture, or following a complete implementation checklist. Triggers on: "build this feature", "implement end-to-end", "new feature from scratch", "set up project structure", "ship this". Covers the Next.js 15 + React 19 + Supabase + Vercel stack.