alliance-platform-docs - SKILL.md Agent Skill

name: alliance-platform-docs description: Answer questions about Alliance Platform package APIs, settings, installation, usage, template tags, and migrations by consulting generated Markdown references. Use for requests involving alliance_platform core, frontend, codegen, storage, audit, ui, pdf, server-choices, or ordered-model docs. compatibility: Designed for filesystem-based coding agents (Codex/Claude Code style). Useful when one or more alliance-platform-* Python libraries are installed or being integrated.

Alliance Platform Docs

Prioritize helping app developers consume Alliance Platform packages: installation, settings, usage patterns, template tags, API behavior, and migrations.

Package Map

Core: shared foundation, package-level configuration patterns, core auth/settings APIs.
Frontend: Vite/bundler integration, React component embedding, template tags and SSR behavior.
Codegen: code generation framework and artifact generation workflows.
Storage: async uploads, storage backends, upload/download flows, management commands.
Audit: model auditing, history/event tracking, audit views, integration patterns.
UI: Alliance UI Django template tags and form rendering helpers.
PDF: HTML-to-PDF rendering setup, deployment, runtime options, and usage details.
Server Choices: server-driven field choices endpoints and serializer/form integrations.
Ordered Model: trigger-backed ordered model behavior and migration guidance.

Consumer-Focused Routing

For setup questions, open each package installation.md then settings.md.
For “how do I use X?” questions, open usage.md/overview.md/templatetags.md first.
For exact APIs, open api.md after behavior is understood.
For upgrade concerns, check legacy-migration.md where available.

Answering Rules

Prefer package-local docs first, then follow cross-package links only when required.
Explain behavior in consumer terms (what to configure, what to call, expected output).
Include concrete setting names, template tags, class/function names, and file paths from docs.
If docs and implementation differ, trust code and explicitly note the discrepancy.