djaiss

Write the documentation for an existing concept.

Write the documentation for an existing feature.

Build a complete API surface from an existing web controller. Use when the user asks to add API methods, expose a resource via API, or mirror a web controller as an API, especially for adminland resources. Activates when user mentions API methods, API controller, API routes, or wants to expose an existing web resource via API.

Write or update the public-facing marketing documentation page for API methods. Use when a new API controller is created, routes are added or changed, or when documentation pages are missing or out of sync with the codebase.

Write or update Bruno API documentation files for a given API controller. Use when a new API controller is created, routes are added or changed, or Bruno docs are missing or out of sync with the codebase.

Use when writing tests. Follow testing best practices, use Laravel's testing tools, and ensure tests are clear, maintainable, and cover relevant scenarios.

Actions are what the user does within an application. Use when working with actions.

Thin HTTP layer controllers. Controllers contain zero domain logic, only HTTP concerns. Use when working with controllers, HTTP layer, web vs API patterns, or when user mentions controllers, routes, HTTP responses.

Write clear, user-focused documentation for the product, including concept explanations, tutorials, how-to guides, and onboarding content. Use when creating or improving documentation pages, help center content, user guides, setup instructions, feature explanations, or task-based walkthroughs. Trigger whenever documentation, docs portal, tutorials, guides, concepts, onboarding, help content, or user education are mentioned.

Analyze the codebase and produce a comprehensive implementation plan for the product documentation portal. Inspect the application's features, terminology, configuration, installation, authentication, subscriptions, permissions, and user workflows to design a documentation structure following industry best practices. Use when planning a documentation portal, defining its information architecture, creating a documentation roadmap, or identifying the documentation required before writing the content.

Write or update the public-facing API reference for API methods. Use when a new API controller is created, API routes are added or changed, or when the docs portal at /docs is out of sync with the codebase.

Build a complete API surface for a given model or concept. Use when the user asks to add API methods, expose a resource via API, or mirror a web controller as an API. Activates when user mentions API methods, API controller, API routes, or wants to expose an existing web resource via API.

Actions are what the user does within an application. Use when working with actions.

Add a new locale to the application. Use when the user wants to support an additional language, register a locale in config, and generate its lang/*.json translation file. Trigger whenever adding a language, new locale, or i18n support is mentioned.

Conventions for writing thin HTTP controllers that validate input and delegate to Actions. Use when creating or editing controllers in app/Http/Controllers (web, API, or marketing).

Use when creating or editing database migrations in the project.

Create or update a journal entry module (database, model, actions, views, controllers, API, docs, tests). Use when adding a new journal module or changing an existing module such as mood, health, or obligations.

Update the README.md file to list all available journal modules under the Features section with categorized, collapsible sections. Use when adding, removing, or reorganizing modules and keeping documentation in sync.

Create or update an Action in app/Actions following JournalOS conventions (validation, logging, queues, tests).

Update the README.md file to list all available journal modules under the Features section. Use when adding, removing, or reorganizing modules and keeping documentation in sync.

Update and complete JournalOS translation JSON files by running composer journalos:locale and fixing missing or empty translations in lang/*.json. Use when UI copy changes, new keys are added, or locale files are out of sync.

Personal relationship manager that helps you stay in touch with important people through gentle nudges, birthday reminders, and conversation tracking.