بنقرة واحدة
git-worktree-setup
Reference this skill whenever you need to understand the worktree setup for this project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Reference this skill whenever you need to understand the worktree setup for this project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
FLS content types, file formats, and frontmatter schemas. Use when authoring a topic, form, quiz, survey, course, course part, chapter, module, or any content file.
FLS course-authoring conventions — numbering, file naming, UUID rules, and HTML-escaping rules. Use when asking about uuid, numbering, ordering, file name, folder, or directory structure.
Define and manage per-app Django settings via per-app config.py modules. Use when adding, reading, or enforcing a setting an app owns, when a downstream project must supply a value, or when the user mentions config.py, AppSettings, declared_settings, required settings, or COURSE_ACCESS_BACKEND.
Write Playwright E2E tests for user flows and browser interactions. Use when testing HTMX, user journeys, or when the user mentions E2E, Playwright, or browser testing.
Write pytest tests. Use when implementing features, fixing bugs, or when the user mentions testing, TDD, or pytest
Every FLS c-* widget — purpose, attributes, and examples. Use when asking about a widget, component, admonition, flashcard, accordion, youtube, picture, table, code block, card, pull quote, or equation.
| name | git-worktree-setup |
| description | Reference this skill whenever you need to understand the worktree setup for this project. |
The project uses a bare repository layout:
main/, some-feature/).git file (not directory) pointing to its git dirTo create a new worktree:
cd .. # navigate to the bare repo (parent of current worktree)
git worktree add <branch-name>
cd <branch-name>
.claude/fls/scripts/install_dev.sh
Each worktree gets its own PostgreSQL database named db_<sanitized_branch> (e.g., db_main, db_feature_auth_flow). This is handled automatically by settings_dev.py which detects the current git branch and derives the database name.
.claude/fls/scripts/install_dev.sh — sets up everything for a new worktree: creates the database, runs migrations, loads demo data.claude/fls/scripts/dev_db_init.sh — creates the per-branch dev and test databases (idempotent).claude/fls/scripts/dev_db_delete.sh — drops the per-branch dev and test databases (for cleanup)