← all publishers

inapp-inc

@inapp-inc source repo

14 published skills

  1. UI UX Pro Max · inapp-inc bundle
    UI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation. Searchable local data: 79 searchable styles (50 active), 192 product palettes and reasoning profiles, 74 font pairings, 119 UX guidelines, 105 icons, 17 GSAP presets, 25 chart types, and 22 stacks.
    0 installs
  2. Rollback And Flags · inapp-inc
    Use when a SEED Unit requires safe rollout, rollback steps, feature flags/config toggles, or risk mitigation. Invoked by spec-driven-development / seed-unit for non-trivial or risky changes.
    0 installs
  3. Security Engineering · inapp-inc
    Use when a SEED Unit has security constraints (authn/authz, tenant isolation, input validation, secrets, OWASP). Invoked by spec-driven-development / seed-unit when security constraints apply.
    0 installs
  4. Performance Engineering · inapp-inc
    Use when a SEED Unit includes performance constraints (latency/throughput/p95/p99, large datasets, UI responsiveness). Invoked by spec-driven-development / seed-unit when performance constraints apply.
    0 installs
  5. Spec Driven Development · inapp-inc
    Use when the user wants work executed through a spec-driven development process. This skill coordinates requirement gathering, architecture, coding, testing, SEED, engineering, and handover skills so implementation follows an explicit spec, changes map back to approved requirements, and validation proves the delivered behavior matches the spec.
    0 installs
  6. Coding · inapp-inc
    Use when implementing features or fixes against an approved spec slice. Applies language- and stack-specific coding guidelines (React, Node, Python, JavaScript, PHP, CI/CD) and keeps code aligned with the spec and OpenAPI contract. Invoked by spec-driven-development for implementation.
    0 installs
  7. Testing · inapp-inc
    Use when implementation needs to be validated against a spec, acceptance criteria, or a defined behavior change. Turns requirements into a concrete test strategy, adds or updates tests, runs validation when possible, and reports coverage and gaps in terms of the spec. Invoked by spec-driven-development after each meaningful slice or before handoff.
    0 installs
  8. Handover · inapp-inc
    Use at the end of delivery to create a holistic handover pack for downstream teams (BAs, architects, developers, QAs, PMs). Invoked by spec-driven-development at closeout.
    0 installs
  9. Scaffold · inapp-inc
    Use for greenfield bootstrap — clone the versioned starter template (Express API, web/Python stubs, Dockerfile, lint, OpenAPI stub) consistent with ADR-0001/ADR-0003, then diverge for project specifics. Invoked by seed-unit for the bootstrap SEED unit after architecture platform-fit.
    0 installs
  10. Seed Unit · inapp-inc
    Use to break work into SEED Units (small PR-sized deliverables) with explicit scope, constraints, acceptance criteria, evidence, and rollback. Produces SEED Unit artifacts and ties them to OpenSpec change folders. Invoked by spec-driven-development after architecture.
    0 installs
  11. Seed Review · inapp-inc
    SEED intent review
    0 installs
  12. Architecture · inapp-inc
    Use when the spec affects system boundaries, data contracts, APIs, persistence, concurrency, security, performance, or cross-team behavior. Applies platform ADRs and governance; produces or updates OpenAPI specs and design decisions. Invoked by spec-driven-development for design and architectural alignment.
    0 installs
  13. Requirements · inapp-inc
    Use when gathering, clarifying, or documenting product or feature requirements. Produces gaps questionnaires and Functional Specification Documents (FSD) so that behavior is explicit, traceable, and usable as input to architecture and implementation. Invoked by spec-driven-development when no usable spec exists.
    0 installs
  14. Observability · inapp-inc
    Use when a change affects runtime behavior and requires logs/metrics/traces, correlation IDs, dashboards/alerts, or evidence of observability. Invoked by spec-driven-development / seed-unit when runtime telemetry constraints apply.
    0 installs