Turn a rough idea into a project plan
Go from a fuzzy idea to a practical build plan with milestones and clear acceptance criteria.
A free library of prompts and agent skills.
Find a starting point. Make it yours. Get going.
Go from a fuzzy idea to a practical build plan with milestones and clear acceptance criteria.
Make a draft clearer and tighter while preserving its meaning and personality.
Connect a product’s value to a specific audience and write a clear first-screen message.
Explore a business idea’s assumptions, alternatives, and cheapest useful validation steps.
Turn an open question into a bounded research plan with credible sources and decision criteria.
Give a design project a clear purpose, audience, scope, and way to judge the result.
Build a realistic weekly plan around capacity, priorities, and existing commitments.
Find missing values, inconsistent formats, duplicates, and questions that could invalidate results.
Build a learning path that connects fundamentals, examples, and practice.
Turn a responsibility into a specific, truthful accomplishment using evidence you provide.
Explore distinct creative directions, then develop the strongest ideas into something usable.
Plan practical meals using your ingredients, time, preferences, and leftovers.
Review code changes for real bugs, edge cases, and actionable improvements.
Turn an ambitious project into a small, testable build plan.
Design tests around behavior, invariants, and plausible failures.
Synthesize supplied material with traceable claims, disagreements, and limitations.
Find actionable accessibility issues in supplied markup, styles, and user flows.
Improve a prompt's goal, context, constraints, and output requirements.
Investigate a reproducible bug with hypotheses, a minimal fix, and a focused regression check.
Get a focused review of correctness, maintainability, and edge cases, grounded in your code.
Map a product workflow into predictable endpoints, validation rules, and error responses.
Choose meaningful tests around a feature’s actual risks and expected behavior.
Build a useful map of a repository and identify where a specific change belongs.
Turn scattered notes into an email with a clear purpose, useful context, and a specific next step.
Reusable instructions for the tools you already use.