Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making mistakes", "this is unintuitive", or "people cant figure out how to use it". Also trigger when reducing product complexity or feature creep. Covers the gulfs of execution and evaluation. For usability scoring, see ux-heuristics. For iOS-specific patterns, see ios-hig-design.

General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.

按问题与证据缺口选择记忆检索范围（8 类题型参考）。 Use when: 任务是 "哪些地方提过 X" / "X 的来源 / source map" / "有没有提过 Y / absence check" / "上次到现在变了什么 / delta" / 冷启动 onboard 复杂主题 / 任何召回任务搜了一刀觉得不够。 Not for: 只是选哪个入口走第一刀（用 memory-navigation）/ 已知精确 anchor 单 Read（直接 Read）/ 代码符号查（Grep/LSP）/ 新功能开发（不是 recall 任务）。 Output: 单一 owner 汇总原始证据、实际覆盖与未验证边界，一次交付。 GOTCHA: memory-navigation 选择入口；本 skill 处理证据缺口与覆盖边界，不按模型家族或固定轮次决定停止。

This skill should be used when code search is needed (whether explicitly requested or as part of completing a task), when indexing the codebase after changes, or when the user asks about ccc, cocoindex-code, or the codebase index. Trigger phrases include 'search the codebase', 'find code related to', 'update the index', 'ccc', 'cocoindex-code'.

Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.

Run a lightweight, evidence-based "sniff test" on a single initiative (epic, project, or Tier-1 bet) to find where its clarity is insufficient for its stage in the Portfolio PDLC lifecycle, so you can drive the right investment/commit and derisking conversations. Best run pointed at where the initiative is managed (its folder/workspace, Confluence space, or Jira epic) or given its Lean Product Canvas plus a recent sponsor update; with little input it asks for context first. Use when pressure-testing an initiative before a Plan/Commit decision or Execute/Build commitment, checking whether a Lean Product Canvas and Discovery plan match the real risks, or coaching on leading indicators and risk-appropriate derisking. For multi-initiative board patterns, use the sniff-test-portfolio add-on.

Run a portfolio-level, product-oriented PDLC (Explore → Discovery → Plan/Commit → Execute → Rollout → BAU, with humans keeping the investment decisions) as an operating loop that leaves the portfolio sharper every cycle, over a plain-file workspace. Use when standing up, operating, or resuming a portfolio of initiatives/epics — seeing where everything is, advancing initiatives with evidence, improving artifact quality and outcome orientation, and continuously improving the process and portfolio construction themselves. Entry point and operating loop for the portfolio-pdlc-* skill family; for one-off diagnostics of a single initiative use sniff-test instead.

White-box assessment of a spec-driven harness or coding-agent configuration from a public GitHub repository, local directory, ZIP archive, or effective instruction hierarchy. Use when a CTO, VPE, or AI adoption leader wants evidence-backed feedback on outcome discovery, trustworthy delivery, in-use validation, and how the harness improves its own loop. For a produced spec as black-box evidence, use pdlc-readiness instead.

Bind a flow workspace to wherever the work is actually managed — GitHub Issues and Projects, Jira, Linear, an internal Kanban dashboard, a spreadsheet, or chat — by choosing a system-of-record mode (files-only, mirror, adopt, split), writing a field-ownership map with exactly one writer per field, and using the board export plus the harness's own tools to sync. Use when leadership needs the flow where they already look, when a tracker already holds the work, or when a sync has started fighting the workspace. Part of the flow-driven family.

Decide what a workflow should measure and wire it in — flow measures (WIP, age, cycle time, throughput, rework), evidence measures (coverage, first-pass yield, escape rate, check agreement), leverage measures (delegate mix, human minutes per item, escalation rate, cost per item), and the outcome measure the stream exists for — with each measure named on the steps that feed it and a baseline taken before anything changes. Use when defining a workflow, when a board has numbers nobody steers with, or before making any workflow-improvement bet. Part of the flow-driven family.

Run the meta-loop — inspect and adapt the workflow itself. Probe the flow (constraint drift, rework hotspots, WIP theatre, decision starvation), the evidence (watermelon steps, checks that always pass, self-graded work), the delegation (rung mismatches, escalation droughts, context rot, platform stall), and the definition of workflow (policy contradictions, silent drift, measures nobody steers with) — then capture improvement bets with benefit hypotheses and kill criteria instead of changing anything on the spot. Use on the meta-loop cadence, after recurring findings, or when the board is clean enough to earn self-improvement. Loop 2 of the flow-driven family.

Docker image build system, Dockerfile structure, image variants, build scripts, and Makefile targets for NIC. Use when building container images, modifying the Dockerfile, adding new image variants, debugging image builds, or working with build scripts.

End-user UX for node_web_interface (React) and web_interface (Flask/templates): entry-level trading terms OK, no pro-trader jargon, minimal UI, situational focus, no AI slop, no em dash in UI strings. Apply on any UI copy, layout, error, or help change.

Use when: scaffolding a new backend entity type, domain module, GraphQL schema, resolvers, or STIX converter in opencti-graphql

Capture screenshots on registered computers, record on macOS or HarmonyOS, and manage saved captures. Probe capabilities before recording.

Draft and submit a well-specified Jira bug report after explicit confirmation. Use when a user wants to report, file, log, or open a bug rather than fix it now.

Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run an audit before.

Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running in its own agent thread, and a spec-editor synthesizer that produces a fold-now / defer-v0.1.1 / defer-v0.2 / reject list plus a ship decision keyed off a 1..10 shocked_meter scale. The orchestrator is the sole writer to the PR: ONE consolidated comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes folds, and renders a ship recommendation that the maintainer weighs.

Connect external services and keep app credentials scoped. Use before adding an API key, OAuth connection, provider setup, or server-side request that needs a user's or workspace's credential.

当用户询问《纳瓦尔宝典》(The Almanack of Naval Ravikant) 相关内容，或在以下领域寻求建议时调用: 财富构建(怎么赚钱/股权期权/杠杆/副业与职业定位/时薪与外包决策)、判断与决策(重大选择纠结/心智模型/打工vs创业)、 幸福与心智(欲望与焦虑/接受与内耗/冥想/刷手机上瘾/愤怒与期望/攀比妒忌)、人生哲学(生命意义/该不该信玄学/诚实沟通/选朋友圈子/怎么读书学习)。 不适用于: 具体投资标的与选股、临床心理治疗、急性危机(先求助专业人士)。 Triggers: 纳瓦尔/Naval/纳瓦尔宝典/致富/财富/幸福/判断力/冥想/读书/人生意义