Results for “inp”
10 skills
czlonkowski n8n-subworkflows
Build reusable, composable n8n sub-workflows with typed inputs, stateless or stateful design, and discoverable naming conventions.
5.7k · bundle
phuryn north-star-metric
Identify a North Star Metric and 3-5 supporting input metrics, classify the business game (Attention, Transaction, Productivity), and validate against seven criteria for an effective North Star.
22.6k
dangquangse srs-generator
Generates an IEEE 830 software requirements specification from raw client input through structured clarification rounds and a review gate.
19 · bundle
More results
dangquangse cl-srs
Generates an IEEE 830 Software Requirements Specification from raw client input through structured brainstorming, gap analysis, and clarification rounds.
19 · bundle
huuanh20 cl-srs
Generates an IEEE 830 software requirements specification from raw client input, guiding users through structured clarification rounds and producing a compliant document.
1 · bundle
wondelai drive-motivation
Design motivation systems for products and teams using Autonomy, Mastery, and Purpose (AMP) to drive intrinsic engagement.
1.6k · bundle
affaan-m product-capability
Translate product intent, PRDs, or roadmap discussions into explicit, implementation-ready capability plans with constraints, invariants, interfaces, and open questions before multi-service work begins.
226k
tinh2 game-ux
Audits game user experience across HUD clarity, menu navigation, tutorial effectiveness, control responsiveness, camera systems, feedback loops, loading screens, and settings completeness. Detects game engine (Unity UGUI/UI Toolkit, Unreal UMG, Godot Control, web-based), maps all UI screens and input contexts.
13
curiositech mcp-server-design
Use when designing, building, or debugging a Model Context Protocol (MCP) server in Node/TypeScript. Triggers: stdio JSON-RPC handshake, tool descriptions as discovery surface, lazy startup vs eager catalog loading, telemetry placement, schema design for tool inputs (zod), tool naming conventions for discoverability, error handling that does not leak stack traces, MCP client compatibility (Claude Desktop, Claude Code, Cursor), local resource fetching, secrets and env var handling, distributing as npm + claude mcp add. NOT for MCP client implementation, MCP HTTP transport (different surface), Anthropic Agent SDK building, or non-MCP plugin systems.
10
subvisual project-context
Use when a project's durable context needs to be seeded or refreshed — creating or updating docs/product/context.md (overview + digest + source index + glossary + Know/Don't-Know ledger + design context + technical context) in the target repo; when a project has no context layer yet (Stage-0 setup); when domain terminology is still forming or has drifted; after a meeting, new evidence batch, or scope change that outdates the current context. Also use to ingest new docs/product/input/ batches into the digest. Do not use for repo scaffolding or CI setup, for writing the discovery plan, PRD, or epics (use discovery-plan, prd-writer, epics), or for creating or revising Jobs to be Done — this skill records finished JTBDs by id and marks missing ones TBD; jobs-to-be-done owns minting them.
0 · bundle