Use for Gredice admin UI work that converts table-based list pages into reusable list views with filter/sort controls above the results, left-aligned primary data, right-aligned tags/actions, and paginated or infinite loading. Trigger for apps/app admin tables, directory entity lists, table-to-list migrations, list item layout reuse, or follow-up pages that should match the operations directory list pattern.
Use for designing or restyling original Gredice garden 3D models, Blender source assets, low-poly/isometric game props, and style direction before runtime entity registration.
Use for Gredice changelog publishing: auditing merged GitHub PRs, selecting user and farmer facing changes, drafting CMS changelog pages, validating metadata/content, and publishing through apps/app CMS and news surfaces.
Use for Gredice API docs/contracts: Hono routes, OpenAPI/Scalar, auth/security, validation schemas, generated directory types, and client helpers.
Use for Gredice CMS page content/tooling: section JSON, admin/public rendering, slug/publish metadata, preview, and CMS routes/schema.
Use for Gredice repo docs: README, CONTRIBUTING, AGENTS, root guides, docs, setup/commands, app/package maps, validation, generated artifacts.
Use for documenting Gredice workflows: delivery, checkout, payments, notifications, inventory, operations, crons, env, and failures across apps/packages.
Use for public Gredice content/SEO in apps/www or status: metadata, structured data, sitemap, Croatian copy, FAQ/legal/product pages, CMS routes.