Your passkey unlocks the same Nostr identity on any device
where it is synced (iCloud Keychain, Google Password Manager).
A new Nostr keypair is derived deterministically from your passkey.
No password, no seed phrase — your passkey is your identity.
Almost there! Passkeys don't work inside apps like X or Instagram.
Tap the ⋯ menu and choose Open in Safari (or Chrome on Android) — your passkey will sign you in instantly.
AgentList
Curated directory of AI skills, agent configs, and MCP servers — ranked by the community.
Drop-in instruction sets that give Claude (or another AI) a specific capability — shareable, reusable, one per task.
AGENTS.md and CLAUDE.md files tell your AI coding assistant how to work in a project — commands, conventions, context. Browse community examples or submit your own.
Model Context Protocol servers connect Claude to live tools and data — file systems, APIs, databases. Self-host or point at a public endpoint.
Configuration files for AI coding tools. Drop a CLAUDE.md, .cursor/rules, or opencode.json in your repo root to shape how the AI codes.
API services that accept direct micropayments via Lightning (L402 protocol) — pay per call, no subscription required. AgentList is a directory only; verify a service before use.
Tip! Simply ask your agent directly to install the skill:
- it's a skill folder, with everything in it directly. easier to ingest than the listing page.
Tip! Share
for the raw content of this listing — easier to ingest in an agent.
API services that accept direct micropayments via Lightning (L402) or X402 — pay per call, no subscription required.
AgentList is a directory only; verify a service before use.
✓ Reviewed
✓ Verified
⚠ Unreachable
Install
Tools
Load in your local or cloud based agent:
scripts/index.html
validformat warning
Discussion
votes
Author
Source
Published
Category
Fetches
Tool
Format
Filename
API Base URL
Pricing
Payment
Triggers a test request to get a Lightning invoice you can pay with any wallet.
---
name: karpathy-guidelines
description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
license: MIT
---
# Karpathy Guidelines
Behavioral guidelines to reduce common LLM coding mistakes, derived from [Andrej Karpathy's observations](https://x.com/karpathy/status/2015883857489522876) on LLM coding pitfalls.
**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
## 1. Think Before Coding
**Don't assume. Don't hide confusion. Surface tradeoffs.**
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
## 2. Simplicity First
**Minimum code that solves the problem. Nothing speculative.**
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
## 3. Surgical Changes
**Touch only what you must. Clean up only your own mess.**
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
## 4. Goal-Driven Execution
**Define success criteria. Loop until verified.**
Transform tasks into verifiable goals:
- "Add validation" â "Write tests for invalid inputs, then make them pass"
- "Fix the bug" â "Write a test that reproduces it, then make it pass"
- "Refactor X" â "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
```
1. [Step] â verify: [check]
2. [Step] â verify: [check]
3. [Step] â verify: [check]
```
Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.
Discussion