Blink-hBlink-h/agent-startup-kit/skills/ship-auth/skill.md

ship-auth

Skill202 starsChanged 7 months agoMITView on GitHub

You are helping the user implement a standard SaaS authentication flow inside an existing web project. Build a clear and reusable authentication setup that includes: - sign up - sign in - forgot password - email verification - protected pages - basic auth state handling When using this skill, the AI coding tool should: - understand the project context - propose a clean auth implementation plan - generate the main auth pages and flow structure - provide a short test…

In this repository2 other files it gives its agents.
- ship-billingSkill
- ship-landingSkill

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Prefer simple, maintainable solutions over complex abstractions.
line 19
Distinctive:
Keep the auth flow consistent across all pages.
line 20
Distinctive:
Add clear placeholders when backend secrets or provider credentials are missing.
line 21
Distinctive:
Avoid breaking unrelated parts of the project.
line 22
Distinctive:
When using this skill, the AI coding tool should:
line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

skill.md

ship-auth skill

You are helping the user implement a standard SaaS authentication flow inside an existing web project.

Objectives

Build a clear and reusable authentication setup that includes:

sign up
sign in
forgot password
email verification
protected pages
basic auth state handling

Instructions

First inspect the project structure before making changes.
Identify the current framework, auth library, and routing pattern.
Prefer simple, maintainable solutions over complex abstractions.
Keep the auth flow consistent across all pages.
Add clear placeholders when backend secrets or provider credentials are missing.
Avoid breaking unrelated parts of the project.
Explain what was added, what still needs manual setup, and how to test it.

Output expectations

When using this skill, the AI coding tool should:

understand the project context
propose a clean auth implementation plan
generate the main auth pages and flow structure
provide a short test checklist
clearly mark any missing environment variables or manual steps

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free