القائمة
Community superstitions - unverified observations from pattern development. Use when encountering undocumented edge cases or framework quirks not in official docs. Verified knowledge should be upstreamed to labs docs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | community-docs |
| description | Community superstitions - unverified observations from pattern development. Use when encountering undocumented edge cases or framework quirks not in official docs. Verified knowledge should be upstreamed to labs docs. |
Location: community-docs/ in community-patterns repo
CRITICAL: These are NOT official framework documentation. Always check
~/Code/labs/docs/common/ first.
Community docs capture empirical observations discovered during pattern development - unverified things that seemed to work but may be coincidence or context-specific.
Location: superstitions/
Single observations only. May be wrong, incomplete, or context-specific.
After checking official labs/docs/ first:
Do NOT consult before official docs - labs/docs/ is always more authoritative!
# Search superstitions
grep -r "Cell.*handler" community-docs/superstitions/
# List superstitions by topic
ls community-docs/superstitions/ | grep "types-"
ls community-docs/superstitions/ | grep "reactivity-"
Upstream it to labs docs instead of keeping it here:
~/Code/labs/docs/common/The goal is for verified knowledge to live in official docs, not here.
Only after solving something not in any docs:
Search first - Check it's not already documented:
grep -r "your topic" ~/Code/labs/docs/common/
grep -r "your topic" community-docs/superstitions/
Create file:
community-docs/superstitions/YYYY-MM-DD-topic-brief-description.md
types-, reactivity-, jsx-, handlers-, llm-,
patterns-, etc.Copy template from community-docs/superstitions/README.md
Include full ⚠️ disclaimer at top
Document:
Commit: "Add superstition: [brief description]"
Remember: You're creating a hypothesis, not stating fact! Be humble about uncertainty.
The blessed/ and folk_wisdom/ directories are deprecated. Previously we
had a three-tier promotion system. Now, verified knowledge should be upstreamed
directly to labs docs.
Skepticism is critical:
Do NOT:
DO:
Superstitions are a safety net for edge cases, not a primary reference!
Sync auto-approved permissions from all community-patterns directories (including community-patterns-2, -3, etc.) to the shared project settings. Shows new permissions for review before adding.
Git operations and pull request workflows. Create PRs, rebase branches, resolve conflicts, merge to upstream. Use when ready to create PR or when working with git branches and upstream.
File framework issues after exhausting other approaches. Document complex problems with multiple failed attempts for framework authors. REQUIRES user permission. Use only after checking docs, community-docs, and trying multiple approaches.
Escalation path when stuck on pattern development. Use when encountering TypeScript errors, framework confusion, unexpected behavior, or blocked progress. Five-step recovery: check docs, study examples, strategic investigation (plan mode + subagents), reset and retry, ask user.
Session initialization sequence for community-patterns development. Use at the start of every Claude Code session. Checks for upstream updates, loads workspace configuration, and ensures dev servers are running.
Proactive recovery using plan mode and subagents. After 1-2 failed attempts, STOP trying variations. Enter plan mode and launch parallel Explore/Plan agents to find idiomatic solutions instead of spinning wheels.