Start, inspect, and stop the @ayunis/ui Storybook for Ayunis Core. Use when reviewing UI package components or stories in a browser.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Run all commands from the Ayunis Core repository root.
./storybook up
Storybook starts in a checkout-specific tmux session and is available at http://localhost:6006. The command waits until the server is ready.
If port 6006 is occupied, do not stop the process using it. Choose another port:
STORYBOOK_PORT=6016 ./storybook up
Use the same STORYBOOK_PORT value for subsequent status, log, and shutdown commands.
./storybook status
./storybook logs
TAIL=200 ./storybook logs
./storybook down
Always stop Storybook through this command. It sends Ctrl-C only to the checkout-specific tmux session created by ./storybook up; never kill a process by PID.
cd packages/ui
pnpm typecheck
pnpm lint
pnpm deps:check
pnpm storybook:build
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Query Ayunis deployed-environment telemetry in AppSignal — incidents, occurrence counts and error traces via the `appsignal-cli` binary; structured log attributes (user.id, org.id, nestjs.context, custom metadata) via the v2 logs API. Use when investigating a production/staging incident or log data — NOT for local dev logs (see backend-debugging).
The English summary is being prepared. Showing the original description.
Ayunis Core backend specifics — module boundaries, key files, and project conventions. Complements the nestjs-hexagonal-backend skill.
The English summary is being prepared. Showing the original description.
Frontend development in ayunis-core. Use when creating, modifying, or debugging frontend code (React, Feature-Sliced Design, API client).
The English summary is being prepared. Showing the original description.
Debug backend runtime errors (500s, crashes, unexpected behavior). Use when something is broken at runtime — not for writing new code.
The English summary is being prepared. Showing the original description.
Shared test fixtures for backend specs — port mock factories, domain builders, and shared IDs in a per-module testing/ folder. Use when a module's *.use-case.spec.ts files repeat the same mock-repository literal, inline entity construction, or hardcoded UUIDs across files.
The English summary is being prepared. Showing the original description.
Analyze Cursor Bugbot PR comments through a root-cause lens: is the finding valid, and is the suggested fix the real fix or a bandaid over a deeper problem? Use when the user asks to check, assess, or triage bugbot comments.
The English summary is being prepared. Showing the original description.