01-core
01Cursor rule Cursor
Pinky core coding hygiene — small diffs, match style, secrets safety.
not rated 4 2mo ago A 133 tokens
original MIT
Cursor rule Cursor
Pinky architecture — boundaries, reuse, extend before inventing layers.
not rated 4 2mo ago A 112 tokens
original MIT
Cursor rule Cursor
Pinky agent behavior — plan large work, verify, respect scope.
not rated 4 2mo ago A 116 tokens
original MIT
04-testing
04Cursor rule Cursor
Pinky testing — behavior-focused checks for non-trivial logic.
not rated 4 2mo ago A 101 tokens
original MIT
05-frontend
05Cursor rule Cursor
Pinky frontend principles — ALWAYS ON until user opts out.
not rated 4 2mo ago A 94 tokens
original MIT
06-backend
06Cursor rule Cursor
Pinky backend principles — ALWAYS ON until user opts out.
not rated 4 2mo ago A 87 tokens
original MIT
Cursor rule Cursor
No AI co-authors — commits and PRs stay under the user's git identity only.
not rated 4 2mo ago A 189 tokens
original MIT
Cursor rule Cursor
If user pastes pinky-cursor repo URL to install — temp clone, install payload only, delete clone, then ask phone channel.
not rated 4 2mo ago C 355 tokens
original MIT
Cursor rule Cursor
Context discipline — load only files needed for the user prompt; do not dump all skills/docs.
not rated 4 2mo ago A 249 tokens
original MIT
Cursor rule Cursor needs its repo
WhatsApp owner phone control via .pinky/whatsapp watch + Cursor CLI.
not rated 4 2mo ago A 301 tokens
original MIT
caveman
11Cursor rule Cursor
ALWAYS ON Caveman — terse replies, fewer tokens, easy to understand user asks.
not rated 4 2mo ago A 248 tokens
original MIT
ponytail
12Cursor rule Cursor
Ponytail, lazy senior — ALWAYS ON until user opts out.
not rated 4 2mo ago A 570 tokens
copy · 91% MIT
Skill Claude CodeCodex
Connect WhatsApp phone control (user-run login + watch + Cursor CLI agent) or Slack MCP. Always ask owner number. Never run QR/login/watch yourself — give commands. After Pinky install channel ask, or /agent-channels / connect WhatsApp.
not rated 4 2mo ago A 56 tokens
original MIT
backend-apis
14Skill Claude CodeCodex
ALWAYS AVAILABLE (Pinky). Stack-agnostic backend and API craft: validation, authz, errors, logging, and safe data access. Use when changing servers, APIs, jobs, auth, or databases. Load only this SKILL.md — not frontend-craft or grill skills unless also needed. Opt out: disable backend-apis / don't use backend skill.
not rated 4 2mo ago A 79 tokens
original MIT
caveman
15Skill Claude CodeCodex
ALWAYS-ON terse communication for Pinky projects. Cuts output tokens (65% measured) by speaking like caveman while keeping full technical accuracy and making user asks easy to understand. Default full on every reply after Pinky install. Supports lite|full|ultra and wenyan-lite|wenyan-full|wenyan-ultra. Use for…
not rated 4 2mo ago A 110 tokens
copy · 67% MIT
Skill Claude CodeCodex
ALWAYS AVAILABLE (Pinky). Stack-agnostic frontend craft for UI, components, pages, CSS, accessibility, and responsive work. Use when building or changing user interfaces. Load only this SKILL.md — not backend-apis or grill skills unless also needed. Opt out: disable frontend-craft / don't use frontend skill.
not rated 4 2mo ago A 71 tokens
original MIT
grill-me
17Skill Claude CodeCodex
ALWAYS AVAILABLE (Pinky). Interview the user relentlessly about a plan or design until reaching shared understanding, one question at a time. Use when user wants to stress-test a plan, get grilled, mentions "grill me", or starts large/ambiguous design work. Load only this SKILL.md — do not load other skills. Opt out…
not rated 4 2mo ago A 84 tokens
original MIT
Skill Claude CodeCodex
ALWAYS AVAILABLE (Pinky). Relentless interview that also writes CONTEXT.md glossary and sparse ADRs. Use when user wants grill with docs, large features needing domain language, or paper trail. Load this SKILL.md first; open CONTEXT-FORMAT.md / ADR-FORMAT.md only when updating those files. Do not load unrelated…
not rated 4 2mo ago A 88 tokens
original MIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: