القائمة
Enforce evidence-based verification before claiming any task is complete
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Learn from corrections, mistakes, and discoveries during conversations. When the user corrects you, when something fails unexpectedly, or when you discover a project-specific pattern worth remembering — record it as a learning so future sessions benefit automatically.
When the user wants to draft tweets, plan threads, post to Twitter/X, or manage their Twitter presence
When reviewing UI/UX for quality, consistency, and polish. Use when the user says 'review the design,' 'check the UI,' 'does this look good,' 'design audit,' 'UX review,' or 'polish the frontend.' Also use after implementing any user-facing feature to catch visual and interaction issues before shipping.
Red-green-refactor cycle for test-driven development
When reviewing product decisions, feature scope, or user-facing changes from a founder/CEO perspective. Use when the user says 'does this make sense,' 'should we build this,' 'review the product,' 'is this good enough,' 'founder review,' 'product sense check,' or before any significant launch. This is the strategic taste layer — not engineering quality, but product quality.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
| name | verification |
| description | Enforce evidence-based verification before claiming any task is complete |
Methodology from obra/superpowers (MIT)
Iron law: no claims without fresh evidence.
Before you say "done", "works", "fixed", or "verified", you MUST:
If you cannot run a verification command, say so explicitly. Never assume.
| Claim | Minimum Evidence |
|---|---|
| "Tests pass" | Paste or reference the test runner output showing green. |
| "Build succeeds" | Show the build command output with zero errors. |
| "Bug is fixed" | Show the reproduction case now producing correct output. |
| "File updated" | Read the file back and confirm the expected content. |
| "Service is running" | Hit the health endpoint and show the response. |
