12 Claude Skills for making the invisible ops of a design team explicit and runnable: mapping how the team works today, then writing the critique ritual, the handoff standard, design-system governance, file conventions, request intake, the capacity plan, a new designer's onboarding, and the handbook that holds them all.
Plugin designops-pack from marketplace 90n-skills in polar-bear-org/claude-skills. Commands read from the repo's manifest — 17 days ago.
capacity-plannerPlans a design team's week, month, or quarter at team level (supply versus demand, what to defer, the wording for saying no), part of the DesignOps Pack by 90n. Use this whenever the user says "run capacity-planner", "can we take this on", "the quarter looks impossible", "plan the team's capacity",
critique-ritual-designerDesigns a design team's critique ritual (cadence, format, roles, rules for givers and receivers, objectives, failure modes), part of the DesignOps Pack by 90n. Use this whenever the user says "run critique-ritual-designer", "design our crit", "our critiques are not working", "set up design critique"
critique-session-preparerPrepares one specific design critique (brief, objectives, framing question, timebox) and afterwards turns the presenter's notes into next steps, part of the DesignOps Pack by 90n. Use this whenever the user says "run critique-session-preparer", "prep my crit", "I'm presenting at critique Thursday",
designer-onboarding-plannerBuilds a 30/60/90 onboarding plan that brings one new designer into the team's ways of working (buddy, first critique, first handoff, first system contribution), part of the DesignOps Pack by 90n. Use this whenever the user says "run designer-onboarding-planner", "a designer starts in two weeks", "o
file-hygiene-standard-writerWrites a design team's file and tool conventions (naming, project structure, cover and status pages, archiving, branching, what lives in which tool), part of the DesignOps Pack by 90n. Use this whenever the user says "run file-hygiene-standard-writer", "how should we name our files", "Figma is a mes
handoff-package-checkerChecks one design handoff package against the team's own handoff standard and lists what is missing as process flags, part of the DesignOps Pack by 90n. Use this whenever the user says "run handoff-package-checker", "is this ready for engineering", "check my handoff", "pre-handoff review", "what am
handoff-standard-writerWrites a design team's definition of ready for design-to-engineering handoff (package contents, states, edge cases, tokens, motion, the conversation), part of the DesignOps Pack by 90n. Use this whenever the user says "run handoff-standard-writer", "define our handoff", "what should a finished desig
request-intake-designerDesigns the front door for design requests (the brief, the triage rules, what gets a yes, a not-yet, or a no, and how the answer is communicated), part of the DesignOps Pack by 90n. Use this whenever the user says "run request-intake-designer", "design request process", "requests come in by DM", "ho
system-change-recorderRuns one proposed design-system change (new component, modification, deprecation) through the team's governance rules and writes the decision record, part of the DesignOps Pack by 90n. Use this whenever the user says "run system-change-recorder", "I want to add a component to the system", "propose a
system-governance-designerDesigns design-system governance sized for a small team (ownership, how changes are proposed and decided, versioning, deprecation, contribution path, decision-record format), part of the DesignOps Pack by 90n. Use this whenever the user says "run system-governance-designer", "who decides on the desi
team-ops-mapperInterviews a design lead and writes the map of how the team actually works today (rituals, handoffs, tools, decisions, pains), part of the DesignOps Pack by 90n. Use this whenever the user says "run team-ops-mapper", "map our ops", "how does our team actually work", "write down our ways of working",
ways-of-working-handbook-writerCompiles every standard and ritual a design team has written into one readable handbook and flags the gaps, part of the DesignOps Pack by 90n. Use this whenever the user says "run ways-of-working-handbook-writer", "put our ways of working in one place", "write the design team handbook", "how we work
42 skills for the whole product job, stage by stage, from the vision to the weekly update, in eight stages: set direction, discover, decide, define, deliver, launch, prove, and run the product. Each skill is named as an action and keeps one framework inside, with the inputs it needs, where it breaks, a fixed output template, a finish line and the next skill to run.
42 skills
41 skills for the documents product people write, from the first brief to the post-launch review: setting up your voice and templates, discovering, shaping the vision, defining the work, deciding, aligning, reporting up, shipping and learning, running the team, and reviewing and editing. Each skill produces one finished document with a named reader and a length budget.
41 skills
The Complete Claude Guide for L&D: 40 Claude skills for the whole L&D job, in eight stages: diagnose the need with the request triage, the performance gap and the action map; work with the experts through the interview, the task breakdown and the review plan; design the learning with objectives, an evaluation plan, a design document and a curriculum map; build and test scenarios, a storyboard, a knowledge check, the check of an AI draft and a learner walkthrough; run the room with a session plan, slides, a facilitator guide and a pilot; carry it into work with a job aid, spaced practice and a manager briefing; measure what changed with a feedback form, an ROI estimate and the one-page report; and lead L&D through the year plan and the business case. For L&D managers and specialists, instructional designers, trainers and facilitators, and L&D leaders. Claude drafts and checks, people decide: nothing a learner does in training is used to grade, rank or build a case against them.
40 skills
Claude for Consultants · Team in Claude: 39 Claude skills for winning and shaping client work when the client has AI too, from their brief to the signed scope, as eight desks in order: Intake reads the client's brief, qualifies the opportunity and records the bid or no-bid decision; Discovery prepares the call, keeps the notes and sends the recap email; Problem writes the problem statement, the issue tree and the hypothesis test plan; Strategy builds options and the recommendation memo; Pricing shapes good-better-best options, fees and a MoSCoW scope; Proposal writes the consulting proposal, the AI use statement and the statement of work; the Client room prepares the walk-through deck, the AI objection answer and the negotiation plan; Follow-through covers follow-up emails, the mutual action plan and the win/loss review. For independent consultants and partners in advisory practices. Claude structures, drafts and checks; it never invents a reference, a result, a number or a client quote, and you run the conversation, make the recommendation and send everything yourself.
39 skills
39 skills for running the whole product cycle with Claude, in seven phases that each hand a named artifact to the next: set Claude up and connect it, frame the question, discover the evidence, decide, build and ship, communicate the call and run the week. Each skill teaches one named, checkable method, with the inputs it needs, where it breaks, a fixed output template and the next skill to run.
39 skills
36 skills for deciding if AI fits, testing it before launch and keeping it honest after: deciding if AI fits, speccing it as tests, briefing the model and the agent, building the evals from real outputs, shipping it safely, running and improving it, and its cost, price and explanation to leaders. Each skill is one named method or one artifact, with the inputs it needs, where it breaks and a fixed output template.
36 skills
Talk like caveman. Cut filler. Keep technical details explicit.
22 skills · 1 command · 3 agents · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.
1 skill
Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications
5 skills · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Package any website or local web build into a lightweight desktop app with Pake CLI.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.