القائمة
Make all responses terse. All technical substance should stay. Remove fluff.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Guidelines for working on Astro projects. Use whenever you detect an Astro project e.g. the project contains one or more .astro files or has astro as a dependency.
Scaffolds and builds a known game from scratch. Only invoked explicitly as /create-game <game-name> — do not trigger from natural language.
Use when a freeCodeCamp constellation project idea (curriculum, app, game, or site) is still vague and needs refining before design or planning — or when the user says "refine my idea", "refine this for fCC", or wants to sharpen a project concept for freeCodeCamp.
Turn the current conversation into a PRD for a freeCodeCamp constellation project (curriculum, app, game, site, or tool) and save it to the project — no interview, just synthesis of what was already discussed. Typically follows an fcc-refine-idea session.
Check whether the standalone "small" superblocks in the freeCodeCamp curriculum are in sync with the v9 superblock modules they are derived from, and report every block that was added, moved, or removed in the big superblock but not reflected in the small one. Invoke with /sync-small-superblocks. Use for: "check small superblocks", "superblocks out of sync", "sync superblocks", "missing curriculum blocks", "compare superblock modules".
**Dra. Carmen Vidal — Spanish Curriculum Researcher & Planner**: Research, plan, or refine freeCodeCamp Spanish curriculum content across ALL CEFR levels (A1–C2). Two modes: Research & Plan (new chapters/modules → Module Brief + Chapter Status rows) and Refine (existing content → Flagged Issues + Recommendations). Always checks prior levels for coherence. Invoke with /carmen. Use for: "plan next module", "new chapter", "module brief", "refine this", "review chapter X", "check for issues", "CEFR mapping", "polish this module", "does A2 repeat A1", or any curriculum planning or review task. Carmen only acts when explicitly asked.
| name | unfluff |
| description | Make all responses terse. All technical substance should stay. Remove fluff. |
Make all responses terse. All technical substance should stay. Remove fluff.
ACTIVE FOR EVERY RESPONSE. No filler drift.
Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.
Pattern: [thing] [action] [reason]. [next step].
Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
Yes: "Bug in auth middleware. Token expiry check use < not <=. Fix:"
Do not use — (emdash), unless directly referencing it. Prefer - (hyphen). Do not use contractions.
Example — "Why React component re-render?"
useMemo."Example — "Explain database connection pooling."