Divine
Official@divinevideo
Your playground for human creativity. Six-second looping videos, built on Nostr — no AI slop.
Agent Skills by Divine
Showing 8 vetted skills indexed across 2 GitHub repositories.
divinevideopr-conventions
Enforce conventional commit formatting and complete PR descriptions for divine-web workflows.
divinevideoproject-structure
Map divine-web source layout and boot flow from index.html to AppRouter.
divinevideocoding-conventions
Define TypeScript, React, hook, and Tailwind coding conventions for the divine-web codebase.
divinevideotesting-guidelines
Define Vitest and Testing Library conventions for deterministic React tests.
divinevideospa-subdomain-root-render
Render React Router SPAs at subdomain roots with edge-injected user data.
divinevideogithub-issue
Create GitHub issues following Epic, Feature, Task, and Bug hierarchy templates.
divinevideoplan
Generate a layer-ordered implementation plan from a GitHub issue.
divinevideogit-worktree-precommit-hook-flutter-failure
Unset git environment variables before Flutter analyze in pre-commit hooks.
Frequently Asked Questions About Divine
FAQPage SchemaWhat specific engineering tasks does Divine support?▼
Divine enables structured project management through GitHub issue hierarchy templates, implementation planning, and rigorous codebase governance. It provides standardized conventions for TypeScript, React, Tailwind, and Vitest, ensuring consistent architectural patterns and deterministic testing across the entire web repository.
Which technical personas benefit from these conventions?▼
Frontend engineers and full-stack developers working on React-based single-page applications benefit most. These standards are designed for teams maintaining complex web architectures who require strict enforcement of commit history, testing methodologies, and source code organization to ensure long-term maintainability.
What are the prerequisites for implementing these standards?▼
Implementation requires a React-based codebase utilizing TypeScript and Tailwind. Users must have a configured environment for Vitest and Testing Library, alongside a standard GitHub repository structure to support the provided issue templates, pre-commit hooks, and PR description enforcement.