SeviaFlow Get Started

AI-Friendly Development

SeviaFlow is designed to work well with AI coding assistants: Resources make the application model and its surfaces explicit, while the documentation and skills give an agent project-specific guidance. The goal is to help people move from an idea to a working application without making up SeviaFlow APIs or rebuilding capabilities the framework already provides.

AI assistance is most useful when it is grounded in the actual Laravel project and installed SeviaFlow version. The skills below guide discovery, planning, implementation, and review; they do not replace developer judgment, tests, or security review.

What AI-friendly means in practice

  • Understand the job before coding. The app-discovery skill interviews the developer about the problem, users, data, workflows, access rules, integrations, and MVP.
  • Map requirements to SeviaFlow. The planner checks the installed package version and distinguishes built-in Resource capabilities from host Laravel work or genuine gaps.
  • Generate code that fits the project. The builder reads the repository's conventions, real package APIs, configuration, examples, and tests before editing.
  • Check both quality and coverage. The reviewer looks for unsafe defaults, missing behavior and tests, and relevant framework features that could replace custom code.

Use framework features when they fit

Based on the application requirements and installed version, an assistant can consider Resources, forms and fields, tables and filters, relationships, actions and bulk actions, workflows, events, import/export, UI pages, dashboards, saved views, API contracts, and OpenAPI. It should use only the features that solve a real need, not add every capability to every project.

For each generated change, the assistant should check the existing Laravel app, the SeviaFlow version in Composer, and the relevant package source or documentation. It should keep model and migration ownership in the host app, register Resources explicitly, verify authorization, and test the resulting behavior.

  1. Run SeviaFlow App Discovery to turn a rough idea into a brief and MVP scope.
  2. Use the App Planner to map that brief to models, Resources, package adapters, access rules, and implementation stages.
  3. Use the Resource Builder to implement an agreed stage in the Laravel repository.
  4. Run the Resource Reviewer against the diff and fix important findings before moving on.

For a small task, call only the skill that matches the task. For a new app, the full sequence gives a beginner a guided path and leaves a reviewable artifact at each stage.

Install the skills

The SeviaFlow skills use the Agent Skills format. Start with installation and example prompts. Claude Code supports project skills in .claude/skills/; other assistants that support Agent Skills can use the same skill instructions from their documented skill directory.

Keep the developer in controlAsk the assistant to show the planned scope, explain assumptions, and run the project's checks. Review generated database and access-control changes before deployment.