Hire an AI full stack developer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A task by task build plan that stays within your spec
• A list of FluxUI and Livewire components for each page
• A theme plan with a light, dark and system toggle in your colors
• A motion plan, and a note on whether a 3D part is worth its cost
• Short code outlines for the key components, marked untested
• A quality check list for speed, motion, mobile and accessibility

How it does the job well

• Read the existing code, its conventions and its tests before changing anything. Match the project's patterns.
• Make the smallest change that fully solves the request. Keep unrelated refactors out.
• Reproduce a bug before fixing it, and add a test that fails without the fix.
• Treat input from users, files and networks as untrusted. Validate it at the boundary.

Mistakes it avoids

• Claiming code works without running it or its tests.
• Inventing APIs, package versions or settings instead of checking the installed ones.
• Changing behaviour outside the request, such as reformatting whole files or renaming public interfaces.

What a good result looks like

An example, not your task: You are building a marketing or product site on Laravel and want it to feel high-end.

• Setup check. Your versions and which of the profile's style guide files you do or do not have.
• Tasks. Each task from your spec with its components, premium touch and done-when line.
• Theme plan. How the light, dark and system toggle works, using your colors.
• Motion and 3D. Where motion or Three.js helps, what it costs in speed and the plain fallback.
• Code outlines. Short outlines of the key Livewire and FluxUI components, marked untested.
• Quality checks. Load time, 60 frames a second, mobile and accessibility checks, each with how to measure.

How the work is checked

• The changed files build, and the relevant tests and linters pass. The commands and results are shown.
• Each change is explained in one line with its reason, and risky areas are named.
• Any check that could not run is reported as NOT_RUN with what it needs.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Read the task list. It takes your spec and tasks as the limit. It does not add features you did not ask for.
• Choose the parts. It picks FluxUI components and Livewire components for each page. It does not add Alpine.js, because Livewire already includes it.
• Plan the theme. It sets up a light, dark and system toggle with your colors, and smooth switching.
• Add the polish. It adds a premium touch to each task, such as spacing, type scale, hover motion and glass-style cards.
• Weigh the 3D parts. It suggests Three.js only where it helps, with a plain fallback.
• Set the quality checks. It lists checks for load time, 60 frames a second, mobile layout and WCAG 2.1 AA accessibility.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id engineering-senior-developer only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/engineering-senior-developer/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your spec or task list, with the pages and features you want
• Your colors, fonts and brand rules for the light and dark themes
• Your setup, such as Laravel, Livewire and FluxUI versions
• Links to sites whose feel you like (optional)
• Your style guide files, if you have them (optional)
• Speed and accessibility targets, if yours differ from the defaults (optional)

Helpful context (optional)

• Your brand colors as hex codes, for both light and dark themes.
• Screenshots of two or three sites with the feel you want.

Tools and access

• Claude, ChatGPT or Gemini: A chat can write the plan. A tool that reads your project files can check the plan against your real code.

Functions and deliverables

• Full stack developer: Plan a polished Laravel and Livewire website build with FluxUI parts, light and dark themes, smooth motion and speed checks.
  • A task by task build plan that stays within your spec
  • A list of FluxUI and Livewire components for each page
  • A theme plan with a light, dark and system toggle in your colors
  • A motion plan, and a note on whether a 3D part is worth its cost
  • Short code outlines for the key components, marked untested
  • A quality check list for speed, motion, mobile and accessibility
  Source: Michael Sitarzewski and Agency Agents contributors.
• Website speed check builder: Share your web app and speed targets. Add Lighthouse checks to your build, with reports for pages that miss the limits.
  • A single Lighthouse config with named budgets
  • A pipeline workflow file
  • Median-of-runs setup to cut flaky results
  • Saved reports for each run
  Source: sickn33.
• Website speed tuner: Give it a page or site code and target pages. Get a measured baseline, ranked fixes and a retest plan.
  • Baseline of Core Web Vitals
  • Causes ranked by impact
  • Image, bundle and caching fixes
  • Target numbers for each fix
  • Re-test plan
  Source: sickn33.
• Succession plan builder: Map your key roles, see who could step in and what each needs to be ready, and get a short board summary. The final calls stay yours.
  • A coverage table with the risk of each role being empty
  • A view of who is ready now and who is ready in 1 to 2 years
  • Talent review prep with a 9-box grid
  • A 12-month development plan for each successor
  • A board summary of 200 words or fewer
  Source: Tuan Duc Tran.
• AI project context organiser: Share your project and next task. Get a short rules file, a focused file list and a clear handoff for later sessions.
  • A ready rules file for your project
  • A list of which files to load for each task
  • Rules for when to reset or trim the session
  • A checklist for spotting drifting answers
  Source: Addy Osmani.

Tasks you can use it for

• You are building a marketing or product site on Laravel and want it to feel high-end.
• You have a spec or task list from a product manager and need it turned into build steps.
• You want a light and dark theme that switches smoothly across the whole site.
• You are weighing a 3D hero section or animations and need to know what they cost in speed.

Limits to check before starting

• Your site is not on Laravel. Use the Frontend developer.
• You want a quick test version to show users this week. Use the Software prototype designer.
• You need the overall system design or database layout. Use the Software architect or the Backend Architect agent.
• You want a finished change checked for bugs. Use the Code Reviewer agent.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the pack from this page and add it to your AI as a skill. If you cannot, paste SKILL.md into a new chat, then references/source-agent.md.
• Paste your spec or task list, your brand colors and your Laravel setup.
• Say "Write the build plan. Ask me once if anything is missing. Do not add features I did not ask for."
• Check that every task in the plan matches a line in your spec. Remove any extra.
• Ask for code outlines one component at a time, then test each in your own project.
• Run the speed, motion and accessibility checks on your real pages. The agent cannot run them.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/engineering-senior-developer for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.