القائمة
Read raw notes in inbox/, classify and label each one, draft what should be drafted in the author's voice, and open the results for review. Never publishes on its own.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Apply WCAG 2 Level AA accessibility standards to design systems, UI components, and web pages — contrast math with a runnable validator, design-token patterns that make color accessible by construction, typography and focus-state rules, and a semantics checklist. Use when building or reviewing UI, choosing colors or type for a brand/design system, setting up design tokens, wiring accessibility checks into a build, or when the user mentions accessibility, a11y, WCAG, contrast, or screen readers.
Detect AI-sounding drift in written content and apply a surgical de-slop pass only where needed. Run on drafts before sending for review.
Engineering leadership principles and decision-making framework. Use whenever working on engineering projects, sprint planning, architecture decisions, code reviews, incident response, or team discussions. Apply these principles proactively.
Voice and drafting guide for all writing meant for other people: posts, articles, updates, messages. Use whenever drafting or editing for an audience. This file handles drafting; the voice itself lives in TASTE.md. If the two conflict, TASTE.md wins.
| name | process-inbox |
| description | Read raw notes in inbox/, classify and label each one, draft what should be drafted in the author's voice, and open the results for review. Never publishes on its own. |
Turn the backlog of raw thoughts in inbox/ into useful, voice-correct output — without ever
publishing on its own.
inbox/.blog — a post idea worth draftingproduct-idea — a feature or product concept to capture and shapetask — something to domemory — a fact worth rememberingdiscard — not worth keepingblog → draft the post with the writing-style skill, run ai-voice-check, save to drafts/product-idea → write a short one-pager (problem, who it's for, why now, smallest version) to ideas/task → add it to your task listmemory → write a small note to memory/discard → archive, no actioninbox/archive/.The label decides what happens to a note. If you run your inbox as files, the label is a line of
front-matter the skill adds. If you run your inbox as GitHub Issues, the same labels map to issue
labels — and a GitHub Action can route on them (see .github/workflows/process-inbox.yml).
blog → drafted into drafts/.product-idea →
shaped into a one-pager in ideas/.Drafting, classifying, capturing — always fine. Publishing, posting, or sending — never without the owner approving that specific item.