all publishers

flpbalada

@flpbalada source repo

123 published skills · page 2 of 2

  1. ▌
    User Story Fundamentals · flpbalada
    Write clear user stories with user, capability, benefit, and testable acceptance criteria. Use when creating or improving backlog items, Given/When/Then criteria, INVEST checks, and user-centered requirements; avoid for roadmap hierarchy, broad requirement audits, or effort sizing.
    24 repo stars
  2. ▌
    Loss Aversion Psychology · flpbalada
    Use loss-aversion analysis when perceived losses outweigh equivalent gains. Use for pricing, trials, cancellations, migration risk, retention, warnings, plan limits, or messaging about what users may lose; avoid fake fear tactics and prefer status-quo-bias skill for resistance to change itself.
    24 repo stars
  3. ▌
    Making Product Decisions · flpbalada
    Make structured product decisions with explicit goals, options, tradeoffs, evidence, and decision records. Use when stakeholders disagree, multiple valid paths exist, scope is contested, or choices need rationale; avoid for requirements cleanup, roadmap hierarchy, or effort sizing alone.
    24 repo stars
  4. ▌
    Explain Yesterday Changes · flpbalada bundle
    Explain changes made yesterday as a simple list. Use when user asks what changed yesterday, what was implemented yesterday, or needs a non-technical change summary from recent git work.
    24 repo stars
  5. ▌
    Playwright Best Practices · flpbalada
    Write, review, or fix resilient Playwright tests around user-visible behavior. Use for locators, web-first assertions, auto-waiting, fixtures, isolation, test data, mocks, projects, trace debugging, and flaky browser tests. For axe, WCAG, ARIA, keyboard, or accessibility-specific scans use playwright-accessibility-testing.
    24 repo stars
  6. ▌
    Prd Requirements Verifier · flpbalada
    Verify completed work against a PRD's Given/When/Then requirements.
    24 repo stars
  7. ▌
    React Use Client Boundary · flpbalada
    Place React and Next.js "use client" boundaries correctly. Use when adding client components, hooks, event handlers, browser APIs, client-only libraries, or fixing Server Component errors about hooks, async clients, or event handlers. Keep data fetching on server when possible and remove redundant directives. For generic React state or effects use their dedicated skills.
    24 repo stars
  8. ▌
    Tailwind V4 Configuration · flpbalada bundle
    Configure Tailwind CSS v4 with the CSS-first setup. Use when installing Tailwind v4, migrating from v3, setting up Vite, PostCSS, CLI, or framework integration, defining @theme tokens, using @source, configuring plugins, debugging content detection, or checking browser support. For component-level utilities, variants, CVA, or tailwind-variants use code-architecture-tailwind-v4-best-practices.
    24 repo stars
  9. ▌
    Typescript Advanced Types · flpbalada bundle
    Design readable advanced TypeScript types. Use when creating reusable type utilities, generics, conditional types, mapped types, template literal types, infer helpers, branded types, type guards, assertion functions, typed libraries, API clients, configs, or state helpers. Prefer simple types until complexity pays off. For broad code-quality typing guidance use typescript-best-practices.
    24 repo stars
  10. ▌
    Typescript Best Practices · flpbalada bundle
    Improve TypeScript safety, readability, and maintainability. Use when reviewing TypeScript code, choosing typing strategy, configuring strictness, handling async errors, replacing any with unknown, narrowing external data, modeling state with unions, placing runtime validation, or organizing types. For complex reusable type utilities use typescript-advanced-types; for interface vs type decisions use typescript-interface-vs-type.
    24 repo stars
  11. ▌
    Docs Grounded Task Context · flpbalada bundle
    Collect project context and documented best practices for clear framework, library, SDK, language, and tool tasks. Use before acting on external APIs or conventions. Stop when directive or target is unclear.
    24 repo stars
  12. ▌
    Nextjs Image Art Direction · flpbalada
    Implement Next.js image art direction with getImageProps(), picture, source, and img. Use when mobile, tablet, or desktop need different image assets, crops, focal points, compositions, or carousel media while keeping Next.js image optimization. Do not use for simple responsive sizing of the same image; use normal next/image sizes for that.
    24 repo stars
  13. ▌
    Visual Cues Cta Psychology · flpbalada bundle
    Guide attention toward the next valuable action with CTA hierarchy, visual cues, and gaze patterns. Use when improving button placement, copy, contrast, page scanning, attention flow, or conversion areas; avoid for broad trust, proof selection, or behavior-change diagnosis.
    24 repo stars
  14. ▌
    Agent Harness Orchestration · flpbalada
    Coordinate multiple coding agents in shared repos with task packets, worktree or branch isolation, path ownership, verification loops, and PR or CI follow-through. Use when supervising ticket-driven multi-agent implementation or conflict-safe execution. Do not use for abstract LLM task splitting without repo state; use orchestrator-workers instead.
    24 repo stars
  15. ▌
    Cognitive Fluency Psychology · flpbalada
    Improve clarity by making content and interfaces easier to process. Use when auditing readability, hierarchy, labels, landing-page copy, onboarding text, or trust created by simplicity; avoid when the main issue is task complexity, choice overload, or staged information reveal.
    24 repo stars
  16. ▌
    Typescript Interface Vs Type · flpbalada
    Choose TypeScript interface vs type aliases. Use when defining object shapes, class contracts, unions, tuples, function aliases, mapped or conditional types, extension patterns, intersections, declaration merging, or reviewing type style. Prefer interface for object shapes and extends; prefer type for unions and advanced aliases. For broad typing strategy use typescript-best-practices.
    24 repo stars
  17. ▌
    Typescript Satisfies Operator · flpbalada
    Choose TypeScript satisfies, type annotations, as const, or assertions. Use when validating config objects, route maps, locale maps, feature flags, status labels, design tokens, or handler maps while preserving literal types; fixing widened types; or requiring exhaustive Record keys. For general interface/type choice use typescript-interface-vs-type; for broader typing strategy use typescript-best-practices.
    24 repo stars
  18. ▌
    Typescript React Smell Detector · flpbalada bundle
    Scan TypeScript and React code for precise signals and contextual hotspots. Use when listing potential code smells for review.
    24 repo stars
  19. ▌
    Playwright Accessibility Testing · flpbalada
    Write, review, or fix Playwright accessibility tests with @axe-core/playwright. Use for axe scans, WCAG A/AA tags, ARIA names, roles, labels, keyboard/focus checks, accessibility audit failures, exclusions, and critical page or flow a11y coverage. For general Playwright locator, assertion, fixture, or flake guidance use playwright-best-practices.
    24 repo stars
  20. ▌
    React Query Server Action Errors · flpbalada
    Handle expected Next.js Server Action errors with TanStack React Query mutations. Use when server actions, mutationFn, useMutation, onError toasts, throwOnError, QueryBoundary, ActionResult discriminated unions, translated error codes, or production-safe client error messages are involved. Do not use for generic React Query data fetching or unrelated form validation.
    24 repo stars
  21. ▌
    What Not To Do As Product Manager · flpbalada bundle
    Identify product-management anti-patterns and replace them with better practices. Use when reviewing PM behavior, stakeholder chaos, vague requirements, output-focused roadmaps, weak discovery, team dysfunction, or PM onboarding; avoid personal critique without concrete behavior and impact.
    24 repo stars
  22. ▌
    Code Architecture Wrong Abstraction · flpbalada
    Decide whether to abstract, duplicate, inline, or split code. Use when creating shared utilities, components, facades, hooks, service wrappers, or DRY/WET refactors; reviewing parameter-heavy helpers, option flags, shallow facades, or premature abstractions. For broad behavior-preserving restructuring use refactoring; for component extraction use decompose.
    24 repo stars
  23. ▌
    Code Architecture Tailwind V4 Best Practices · flpbalada
    Choose Tailwind CSS v4 component styling patterns. Use when building Tailwind components, buttons, cards, variants, slots, state styles, or design tokens; choosing utilities vs CVA vs tailwind-variants; avoiding @apply; or migrating v3 component patterns. For project-level Tailwind installation, PostCSS/Vite setup, @source, plugins, or browser support, use tailwind-v4-configuration instead.
    24 repo stars