k2f-checklist
Blueprint operational, launch, diligence, or readiness checklists with phased flow, verifiable items, and scannable hierarchy—not a flat bullet dump or generic productivity template. Use when the user asks for a checklist, pre-flight list, deploy runbook checks, onboarding steps, audit tracker, or "what do we need before we ship." Create checklists 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.
- Installs
- 677
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/suzheng/k2f --skill k2f-checklist- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads k2f-checklist automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
K2F Checklist — AI-Native Aesthetic Design
Purpose
Teach agents to blueprint checklists in content_and_design.md: what must be verified, how to group and sequence items, and aesthetic intent (scanability, checkbox rhythm, operational tone)—without inventing org policy, compliance gates, or thresholds the user did not supply.
Built on K2F
This skill produces checklists as .K2F packages. Follow the k2f skill for authoring: unpack or init a workspace, edit the semantic tree, pack/verify, and export. K2F keeps agents on meaning—sections, item labels, check states—not coordinates.
Before you build, install the core skill: npx skills add suzheng/k2f --skill k2f.
When to Use
- Pre-launch, deploy, migration, event, travel, or handoff verification the user will run repeatedly or once under time pressure.
- Consolidating runbooks or diligence lists into one printable or fillable checklist.
- Multi-workstream readiness when grouped sections beat a flat list.
Workflow
Step 1. Generate the content_and_design.md
Single blueprint for checklist content and design intent. Use labeled blocks (title band, context line, sections, checkbox rows, triggers, notes) the k2f skill can map later.
Sub-steps
-
Checklist frame — Domain, who runs it, one-shot vs recurring use, and page budget (often one page per phase). Tone: calm procedural, time-critical deploy, or formal compliance.
-
Scope & requirement audit — Gates, tools, risks, approvals, and decision criteria (stop, rollback, escalate). Unknowns →
OPEN QUESTIONorNEEDS USER INPUT; never fabricate SLAs or thresholds. -
Information architecture (include / cut / merge) — Choose the dominant spine:
- Chronological phases when order matters (e.g., Pre → Execute → Post; Plan → Pack → Go).
- Parallel workstreams when teams advance independently (finance, legal, ops)—each section self-contained.
- Hybrid only when needed; phase headers with workstream sub-blocks. Default blocks:
- Title & context → checklist name, date/version slot, owner or role if supplied.
- How to use (2–3 lines): when to run it, estimated time, what “done” means.
- Core sections → themed groups with 4–12 items each; prefer verbs + observable outcome (“CI green on release branch”) over topics (“Testing”).
- Triggers / exceptions → rollback, stop-ship, or escalation lines the user defined.
- Optional appendix intent → links, ticket IDs, or data-room pointers—not duplicate checklist items. Cut vague items (“double-check quality”), duplicates across phases, narrative paragraphs, and nice-to-haves that do not gate the stated goal.
-
Item contract pass — One action, one verifiable done state per row; parallel verbs across siblings. Add priority or owner only when requested. Pair “If yes…” follow-ups under the parent.
-
Customization pass — Add context-specific sections (migrations, flags, sector items) only from user input or named templates. Keep stable section order for recurring use.
-
Design intent — Tone: direct; urgency via section labels, not alarm copy. Hierarchy: title, context, then section heads over checkbox rows. Density: split long undifferentiated lists. Rhythm: one line per item; triggers separated from routine rows. Brand: restrained accent; print-friendly contrast.
Log assumptions (section order, omitted optionals) vs open questions (missing thresholds, owners, or policy text).
Rules & constraints
- Verifiability gate: every item answers “how would I know it’s done?”—if not, rewrite or cut.
- Truth gate: approvals, environments, metrics, and legal steps trace to user input or explicit stubs.
- Scope gate: document in / out of scope for this checklist; post-checklist workflow is one line, not a runbook essay.
- One-action gate: split compound rows (“review and deploy and notify”) into separate items or ordered sub-steps.
- Gate ordering: blockers (tests, approvals, backups) appear before irreversible steps in chronological checklists.
- Living-doc gate: note status-tracking intent only when requested; do not invent status enums.
Common failure modes
- Flat laundry list with no phases or themes → regroup by time or workstream.
- Items before prerequisites (“deploy to prod” before “staging verified”) → reorder chronological spine.
- Missing triggers or rollback lines when user mentioned risk → add triggers section or flag
NEEDS USER INPUT. - Generic template ignoring user stack → inject only user-named tools and gates.
- Essay instructions replacing checkable rows → convert to checkbox items plus a short how-to-use block.
- Duplicate checks in every phase → keep once at the earliest gating section.
Quality checklist
- Frame, page budget, tone, and requirement audit (gates, tools, triggers) documented.
- IA choice (phases, workstreams, or hybrid) explicit; in/out scope and cuts explained.
- Every item is one verifiable action with parallel wording; follow-ups tied to parents.
- Triggers/stop conditions present or stubbed; assumptions vs open questions listed.
- Design intent covers tone, hierarchy, density, rhythm, and brand for the full checklist.
Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.
Follow k2f skill to instantiate sections and checkbox items from the blueprint, apply design intent, verify, and export the runnable checklist (typically fillable PDF or DOCX).
FAQ
What does the k2f-checklist skill do?
Blueprint operational, launch, diligence, or readiness checklists with phased flow, verifiable items, and scannable hierarchy—not a flat bullet dump or generic productivity template. Use when the user asks for a checklist, pre-flight list, deploy runbook checks, onboarding steps, audit tracker, or "what do we need before we ship." Create checklists 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.
How do I install k2f-checklist?
Run npx skills add https://github.com/suzheng/k2f --skill k2f-checklist in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/k2f-checklist/ (personal) or .claude/skills/k2f-checklist/ (project).
Which AI agents can use k2f-checklist?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is k2f-checklist safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains k2f-checklist?
It is published by suzheng in suzheng/k2f. It has 677 recorded installs.
More from suzheng/k2f
k2f-worksheet
suzheng/k2f
Design printable, fill-in-ready worksheets—practice sets, graphic organizers, lab records, reflections, or gap-closure forms—from learning goals and source material. Use when the user asks for a worksheet, handout with answer spaces, practice problems, graphic organizer, or structured questions students complete in class or at home. Create worksheets 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.
k2f-quotation
suzheng/k2f
Create client-ready sales quotations from scope notes, line items, rates, and terms—structured so buyers can compare options, accept, or convert to an invoice without rework. Use when the user asks for a quotation, quote, estimate, proposal pricing, or RFQ response. Create quotations 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.
k2f-idml
suzheng/k2f
Blueprint multi-page print publications—brochures, magazines, catalogs, annual reports, lookbooks—for designer handoff with spread-aware story flow, typed editorial blocks, and art direction before layout. Use when the user asks for InDesign, IDML, editorial layout, print collateral, or an editable package for a production designer. Create idmls 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.
k2f-sales-deck
suzheng/k2f
Turn discovery notes, proposals, and product proof into buyer-ready sales decks with a prospect-centered story, one objective per meeting, and evidence-backed slides. Use when the user asks for a sales deck, demo presentation, proposal deck, executive briefing, or sales slides (not a fundraising pitch deck or generic company overview). Create sales decks 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.
k2f-invitation
suzheng/k2f
Turn event facts and tone notes into print or digital invitations with ceremonial copy, layered logistics, and suite-consistent visual intent—not posters, programs, or slide decks. Use when the user asks for a wedding invitation, party invite, gala card, save-the-date, RSVP insert, or mobile e-invite. Create invitations 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.
k2f-flyer
suzheng/k2f
Turn event details, offers, or brand notes into a single-page flyer with a scannable headline, one primary call to action, and mood-matched visual intent—not a brochure, slide deck, or poster wall. Use when the user asks for a flyer, leaflet, handout, promo sheet, open-house sheet, or print/digital one-pager for events, sales, restaurants, fitness, real estate, hiring, or community campaigns. Create flyers 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.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.