Freedom-LS

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.

When and how to convert messy Markdown into valid FLS content structure. Use when converting, restructuring, or importing markdown, or when pasting content into FLS.

Best practices for code comments, docstrings, and inline explanations in the FreedomLS codebase, plus how to clean up stale or noisy comments. Use whenever you write or review a comment in Python, Django templates, JS, or CSS — and especially while implementing a spec/plan/research doc, so section citations (§4b, spec §6.1, per plan §8) never leak into the code. Consult this whenever you catch yourself writing a comment that restates the code, narrates implementation history, or points at an external document.

How to use Alpine.js for client-side interactivity. Use when adding interactive behaviour to templates such as toggles, dropdowns, modals, expand/collapse, dismissible elements, or any client-side state.

How Claude Code actually works when authoring commands, skills, and agents — what works and what doesn't. Use when writing/editing a slash command, skill, or agent definition, designing subagent fan-out, choosing a model tier, or whenever you need to know how Claude Code subagents/skills/models behave. Targets Claude Code 2.1.x.

Create or edit Django templates with cotton components, template partials, and proper Tailwind usage. Use when creating/editing HTML templates, adding components, or when the user mentions templates, UI, or frontend work.

Audit `.claude/settings.json` (shared project settings) for entries to add, remove, or rewrite, using `.claude/settings.local.json` as a hint for useful permissions. Only edits `.claude/settings.json`. Use when the user asks to "tidy up project settings", "audit project settings", or "promote permissions to project settings".

Configure signup, T&C/Privacy consent, legal documents, and post-verification registration forms via SiteSignupPolicy. Use when configuring the signup flow, adding/editing legal documents under legal_docs/, writing a registration form that gates platform access, or querying LegalConsent.

Reference this skill whenever you need to understand the worktree setup for this project.

Use Playwright MCP to interactively browse, inspect, and interact with the running dev site. Use when the user asks you to look at a page, check how something looks, click through a flow, fill in forms, or debug UI issues in the browser.

FreedomLS brand identity, visual system, and voice guidelines. Use whenever building UI, writing copy, creating templates, choosing colours/fonts, or making any design or communication decision for the FreedomLS project. This includes: HTML/CSS/Tailwind styling, Django templates, README content, documentation, error messages, marketing pages, emails, social posts, and component libraries. If you are writing code or content that a human will see in a FreedomLS context, consult this skill.

Configure Django admin with Unfold and SiteAwareModelAdmin. Use when creating/modifying admin classes, working with inlines, or when the user mentions admin interface.

Frontend styling with Tailwind including applying classes to templates and components, creating UI elements, reviewing markup, modifying component classes, and building Tailwind.

Use this skill when making use of any icons in any part of the frontend.

Work with markdown content system, MarkdownContent models, and cotton components in markdown. Use when working with content models or adding markdown components.

Work with Django Sites framework, SiteAwareModel, and site isolation. Use when creating/modifying models, working with multi-tenancy, or when site context is involved.

Use when completing tasks, implementing major features, or before making commits.