Packs

3 packs

Create Onboarding Documentation

Generate audience-tailored onboarding guides for a codebase with architecture maps and entry points.

3 skills · pack

Generate Codebase Documentation

Analyze a codebase and produce architecture docs, onboarding guides, and a README for new contributors.

10 skills · pack

Onboard to Codebase

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and AGENTS.md.

10 skills · pack

Results for “onboarding”

5 skills

understand-anything

Analyzes a codebase with multiple agents and builds an interactive React knowledge graph dashboard for onboarding and visual architecture exploration.

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

Design or improve onboarding flows, empty states, and first-time user experiences. Helps users get started successfully and understand value quickly.

More results

Use this skill when creating, redesigning, critiquing, reducing, polishing, hardening, or making design decisions for a user-facing interface, brand surface, product UI, component, dashboard, flow, app shell, onboarding, empty state, or visual system. Applies Mies van der Rohe-inspired restraint, the Interface Craft workflow, and anti-generic design discipline. Not for backend-only work.

theycallmeholla

Reconstruct a product flow, then audit how usable it is — whether it makes sense, where users get confused or stuck, whether the copy and instructions are clear, and where friction causes drop-off. Produces a prioritized, severity-weighted findings report. Works from three inputs: frontend code in a repo, a live running app driven via a browser, or a written flow / spec / screenshots. Use this skill whenever the user asks for a UX review, usability audit, "is this flow confusing", "does this signup/onboarding/checkout make sense", "why are people dropping off", "audit this form", "where's the friction", or hands over a flow and asks whether it's user-friendly. Trigger even on casual phrasings ("is my checkout any good?") — it imposes the structure ad-hoc UX opinions miss. Audits flow usability and friction; for visual polish and interface quality the impeccable audit/critique skills apply instead.