Loading...
Loading...
Found 863 Skills
Mengubah ide aplikasi singkat menjadi PRD dan spesifikasi teknis siap implementasi.
Finds and finishes the last 20% of a built solution — the experiential layer agents skip: what the output actually reads like, which pages or screens should exist, first-run and empty states, opinionated defaults, the golden path. Use when planning any build so the magic gets specced as concretely as the plumbing, before calling any build "done", when a solution works but feels like a demo, or when the user says "last 20%", "finish this", "make it actually good", "is this actually done", or "why does this feel flat".
Turn the approved PRD into a technical blueprint the build can follow — stack, where it runs, components, data, file structure — calibrated to the learner and sized to a proof of concept. The last planning step before code. Run after 3-prd.
Decide whether one GitHub issue is valid, unique, scoped, and ready to proceed.
Create a hedera-harness recipe — PRD, recipe file, validators, and optional stages — by grilling an idea into a runnable feature spec. Use when the user wants to turn a Hedera feature idea into harness inputs.
Interview user in-depth to create a detailed spec
Shared vocabulary for hedera-harness recipes — the files, the v3 defaults, the stages, and the blind/evaluate-checklist rule. Use when authoring or auditing a harness recipe, or when another skill needs the recipe vocabulary.
Define project UI/UX design specs and output design-spec.md, review existing interfaces and deliver prioritized fix recommendations, or compile design rules for specific surfaces. Use when the user asks for a design system, design spec, or full UI review; simple questions about a single color, font size, or button size get a direct answer.
Write and review a business-level App Spec — domain model, workflows with ROI, stories with failure paths, platform gap mapping in atomic commits, phased rollout — before any feature spec exists. Feeds om-spec-writing via feature briefs. Use for "create an app spec", "define business requirements", "what should we build".
Orchestrated, idea-to-plan PM workflow. Establishes context once, then composes the PM generative ladder in order — problem → discovery → users → riskiest-assumption test → prioritization → spec → metrics — gating each step, enforcing evidence before the spec, and handing the result to product-review. Trigger when the user wants to go from a raw idea to a build-ready plan ("take me from problem to plan", "I have an app idea, where do I start", "turn this idea into a product plan", "plan a new product end to end") — but NOT when they ask for one specific PM artifact (let that skill trigger directly), and NOT for the strategy/launch arc (vision, competitive analysis, roadmap, GTM — offer those next).
Plan, produce, adapt, finish, deliver, and improve platform-ready short vertical social videos from a brief, script, transcript, or source media. Use for TikTok videos, Instagram or Facebook Reels, YouTube Shorts, LinkedIn vertical clips, and cross-platform social cutdowns when the work requires audience and objective definition, an honest hook and promise, short-form beat or shot planning, UI-safe layout, captions and accessibility, speech/music/SFX mixing, platform-specific exports, rights and AI or sponsorship disclosure, analytics-led retention iteration, or final QA and repair. Do not use as a provider-specific image, video, voice, or music generation guide.
Use when designing or writing a new package, procedure, function or trigger, or restructuring one - "viet package", "tao procedure", "them function", "them trigger", an API another team will call, an error-handling or logging design, a spec change. Applies the industry-standard PL/SQL design rules - the spec as a contract, named exceptions, one transaction owner, thin triggers - beneath the house conventions, which always win.