furystack

Create a Shade component from scratch. Use when the user asks to create/add a component, page, widget, dialog, form, or any UI primitive built with @furystack/shades.

Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.

Implement a new physical store backend (e.g. file system, MongoDB, Redis, custom) for FuryStack and expose it via a `defineXxxStore` helper. Use only when the user asks to add a new store/adapter package or extend an existing one with a new backend.

Review all changes on the current branch. Use when the user asks for a code review or PR review.

Author Vitest unit, Vitest integration, or Playwright E2E tests for FuryStack code. Use when the user asks to write/add/cover tests for a function, module, package, component, or flow.

Add a REST endpoint to the app — type contract in common, validation schema, action implementation, registration, tests, changelog. Use when the user asks to add/expose/create a new endpoint, route, REST API, or wants to convert a function into an HTTP-callable action. Branches between custom actions and DataSet-backed CRUD.

Create a Shade component from scratch. Use when the user asks to create/add a component, page, widget, dialog, form, or any UI primitive built with @furystack/shades.

Review all changes on the current branch. Use when the user asks for a code review or PR review.

Wire a new entity into the data layer — model, store binding, DataSet with authorization/hooks, optional entity sync. Use when the user asks to add an entity, persist a model, expose a collection, or set up a new DataSet.

Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.

Add a REST endpoint to the app — type contract in common, validation schema, action implementation, registration, tests, changelog. Use when the user asks to add/expose/create a new endpoint, route, REST API, or wants to convert a function into an HTTP-callable action. Branches between custom actions and DataSet-backed CRUD.

Review all changes on the current branch. Use when the user asks for a code review or PR review.

Wire a new entity into the data layer — model, store binding, DataSet with authorization/hooks, optional entity sync. Use when the user asks to add an entity, persist a model, expose a collection, or set up a new DataSet.

Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.

Add a REST endpoint to the app — type contract in common, validation schema, action implementation, registration, tests, changelog. Use when the user asks to add/expose/create a new endpoint, route, REST API, or wants to convert a function into an HTTP-callable action. Branches between custom actions and DataSet-backed CRUD.

Review all changes on the current branch. Use when the user asks for a code review or PR review.

Wire a new entity into the data layer — model, store binding, DataSet with authorization/hooks, optional entity sync. Use when the user asks to add an entity, persist a model, expose a collection, or set up a new DataSet.

Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.

Review all changes on the current branch. Use when the user asks for a code review or PR review.

Fill changelog entries for the current branch. Use when the user asks to fill changelog, write changelog entries, update changelog, or prepare changelog for a PR.

Review blog posts for the FuryStack site. Use when the user asks to review a blog post, check tagging, validate frontmatter, or verify post conventions. Also use when a branch contains new or modified posts and the user asks for a review.