Loading...
Loading...
Found 11 Skills
Use when organizing, critiquing, or implementing navigation, labels, taxonomy, hierarchy, search, content grouping, or wayfinding for a digital product.
Structure information so people can find what they need, understand where they are, and navigate confidently. Covers navigation pattern design, taxonomy, labeling systems, search and browse strategy, wayfinding, and IA research methods. Trigger when designing navigation structures, categorization schemes, site maps, taxonomies, labeling systems, search experiences, or asking "how should we organize this?" Also trigger for card sorting, tree testing, information findability problems, or when users report they can't find things. Use this skill any time the structural organization of information is the problem — not the flow through it, not the words in it, not the visual presentation of it.
Design the general-attendee on-site journey for a technical event - check-in desk and badge pickup, the badge's privacy and scanning posture, wayfinding and signage, the quiet room and other facilities, meal and dietary mechanics, the help path, first-time-attendee orientation, and a walkthrough audit of the finished design. Use whenever asked how to run conference check-in, whether to put a QR code on a badge, where the quiet room goes, how to sign a venue so people find rooms, how to hand out dietary-restricted meals, what a help desk should cover, or how a first-timer finds their feet. Starts at the door. Do NOT use for registration or no-show mechanics - use samber/dev-event-organizer-skills@event-no-show-management; speakers, sponsors and volunteers have their own journey skills.
Turn confirmed schedules, social slate decisions, and sponsor lists into attendee-facing programs with time-first wayfinding and publish-safe social copy—not posters, invitations, or slide decks. Use when the user asks for a conference program, festival booklet, gala run-of-show, performance playbill, or multi-day badgeholder agenda. Create event programs with AI-native design and the highest aesthetic standards, powered by the K2F format and engine. Purpose-built for AI agents, K2F lets them focus on semantic content and design intent while automatically handling layout, typography, and formatting complexity.
Designs, deepens, and hardens TypeScript codebase architecture in three modes: folder structures, module contracts, and middleware pipelines for a new app; domain-informed deepening of existing code; and the guardrail tooling, CI gates, and wayfinding that stop a structure decaying. Use when setting up project structure, organizing a monorepo, designing backend modules, writing an architecture brief, recovering domain terminology, recording an architecture decision, or asking "how should I structure this app", "find architecture improvements", "this module is a mess", "make this codebase agent-friendly", "set up guardrails for coding agents", "add a dead-code check", or "my agent can't find anything in this repo". For scaffolding a new repo use scaffold-nextjs or scaffold-cli, for multi-tenant isolation use multi-tenant-architecture, for the AGENTS.md file's own content use agents-md, and for review of a local diff use pr-reviewer.
Use when animating navigation bars, menus, sidebars, or wayfinding elements to create smooth, intuitive transitions
Route engineering work to the right next workflow from natural-language intent and current project state. Use when the user asks what to work on, wants to start something new, continue existing work, pick up a project, decide what comes next, or needs help choosing between research, wayfinding, specification, ticketing, implementation, testing, or review. Infer the lightest safe route, inspect repository and GitHub state when useful, visualise progress top-to-bottom, and stop before execution until the user explicitly authorises the recommended next action.
Shipyard's navigator — chart a foggy effort (destination unclear, questions not yet stateable) into a map of decision tickets on the repo's issue tracker, then work the frontier one ticket per session until the way is clear, and hand the collapsed decisions to /launch as a mission brief. Wayfinding, not building: it produces decisions, never deliverables.
Spatial planning for buildings: floor plan layout and archetypes, circulation design (corridors, stairs, elevators, escalators), core design and vertical service distribution, vertical stacking strategy, net-to-gross optimization, space efficiency metrics, wayfinding, and spatial legibility.
Select and design navigation patterns that match product structure, user tasks, and platform conventions.
Lập bản đồ cho một chunk việc QUÁ LỚN với một phiên agent và còn MÙ MỜ — dựng một bản đồ các ticket QUYẾT ĐỊNH trên ledger issue, rồi giải từng ticket một cho tới khi đường tới đích hiện rõ. Gọi bằng tay khi có một ý tưởng lớn chưa rõ hình dạng, TRƯỚC cả /propose. Chỉ-gọi-tay.