Skip to content

AI-Assisted Engineering

AI accelerates implementation. Requirements, architecture, business rules, data modeling, review, tests, security and accessibility stay with me.

I should be able to understand, explain, debug, modify and validate the code I ship.

Workflow

AI takes part in one step. Everything around it is still engineering.

  1. Requirements
  2. Business rules
  3. Architecture
  4. AI-assisted implementation
  5. Human review
  6. Testing
  7. Lint / typecheck
  8. Security review
  9. Documentation
  10. Delivery

What stays with me

  • Defining requirements and business rules.
  • Defining the logic and the data models.
  • Understanding and deciding the architecture.
  • Reviewing every piece of generated code.
  • Validating behavior with tests, types and lint.
  • Considering security and accessibility.
  • Making the documentation reflect the real behavior.

Where AI helps

  • Implementing tasks whose requirements and logic I have already defined.
  • Supporting the consistent application of good practices.

Review checklist

What I verify before accepting generated code:

  • It does what was specified, nothing more.
  • It follows the project architecture and rules.
  • Types are correct: strict mode, no unnecessary any.
  • Lint and typecheck pass without disabling rules.
  • Tests verify behavior, not implementation details.
  • Inputs are validated and no secrets are exposed.
  • It is semantic and operable with the keyboard.
  • Documentation matches the real behavior.

Example

An illustrative task specification and the kind of review notes it leads to.

task-spec.mdIllustrative
Task: add pagination to the users table

Requirements
- Page sizes: 10, 25 and 50
- Loading, empty and error states
- Filters and sorting keep working across pages

Constraints
- Go through UserService, never the mock data directly
- Strict TypeScript, no new dependencies

Done when
- Behavior tests pass
- Lint and typecheck are green
review-notes.mdIllustrative
- Page size is not validated -> add a schema check in the service
- Component imports mock data -> move it behind the repository
- Empty state is missing -> add it and cover it with a test
- Page buttons have no accessible names -> add labels

Development workflow

Cursor and Claude Code are part of the workflow, not a substitute for the stack. This repository includes Cursor rules (in .cursor/rules) that the tools have to follow.