القائمة
Create or update feature documentation in the Astro Starlight docs site. Use when adding new features or updating existing documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Launch, build, run, start, screenshot, or smoke-test the Librariarr Next.js webapp end-to-end. Use when asked to run librariarr, bring up the dev stack, take a screenshot of the dashboard or any UI page, verify a change in the running app, or check that the app boots cleanly.
Generate a new Next.js API route with project boilerplate (auth, validation, sanitize, Prisma). Use when creating new API endpoints.
Generate an integration test for an API route with all required mocks and boilerplate. Use when creating tests for API endpoints.
Quick reference for all Librariarr project conventions and patterns. Consult when writing or reviewing code to verify correct patterns.
Create a Prisma migration file for schema changes. Required for production — db push only works in dev. Use after modifying schema.prisma.
Scaffold a complete new feature end-to-end (Prisma model, migration, schemas, API routes, tests). Use for new CRUD resources or features that span multiple layers.
| name | doc-feature |
| description | Create or update feature documentation in the Astro Starlight docs site. Use when adding new features or updating existing documentation. |
| argument-hint | <feature-name> [new|update] |
Create or update documentation for: $ARGUMENTS
The docs site is completely isolated from the Next.js app:
package.json, tsconfig.json, build toolchaindocs/src/content/docs/docs/docs/astro.config.mjsdocs/src/content/docs/docs/
getting-started/ — Installation, configuration, server setup
features/ — Dashboard, library, lifecycle rules, stream manager, etc.
integrations/ — Sonarr, Radarr, Lidarr, Seerr, Plex, Jellyfin/Emby
advanced/ — Development guide
---
title: Feature Name
description: Brief description for SEO and link previews.
---
Content here using standard Markdown.
## Section Heading
Use Starlight components for rich content:
- `:::note` / `:::tip` / `:::caution` / `:::danger` — callout boxes
- `import { Tabs, TabItem } from '@astrojs/starlight/components';` — tabbed content
- `import { Steps } from '@astrojs/starlight/components';` — numbered steps
New pages must be added to docs/astro.config.mjs:
// In the sidebar array, under the appropriate section:
{
label: "Features",
items: [
// ... existing items
{ label: "New Feature", slug: "docs/features/new-feature" },
],
},
The slug must match the file path relative to docs/src/content/docs/ without the .mdx extension.
docs/src/content/docs/docs/<category>/<name>.mdxtitle and descriptiondocs/astro.config.mjs under the correct sectionpnpm docs:build (catches broken links/formatting)docs/src/content/docs/docs/pnpm docs:build