Find agent skills by outcome

- Use clear

concise scientific language.

Return only the final generated prompt (or clarification questions

if required).,FALSE,TEXT,[email protected]

- Constraints (tone

length

- Output format (explicit structure

e.g.

- Clear

concise

- Use placeholders for customizable elements

formatted like: ``

- Identify the goal

desired output format

Now ask me about my project

or generate a CLAUDE.md if I've already provided enough detail.,FALSE,TEXT,ahmetaligul01

- Tech stack (languages

frameworks

Before generating the final file

verify:

If I provide minimal info

ask me targeted questions to fill the gaps — but never more than 5 questions at a time.

For DB migrations

see @prisma/README.md

- Branch naming

commit message format

- Project name

one-line purpose

- Build

test (single file + full suite)

7. Verify

don't trust. Always include how to verify changes (test commands

4. Actionable

not theoretical. Only include instructions that solve real problems — commands you actually run

3. Progressive disclosure. Don't inline lengthy docs. Instead

point to file paths: For auth patterns

1. Conciseness is king. The final file MUST be under 150 lines. Every line must earn its place. If C...

omit it.

prompt: A curvy but slender thirty-year-old woman with wavy brown hair dances wildly on a nightclub...

eyes open

Night club

{

• Move fast

but not so fast that I can’t follow what’s happening.

• Treat me as the product owner. I make the decisions

you make them happen.

• Make it look professional

not like a hackathon project