Skip to main content

Software Engineer Agent

File: .github/agents/tsh-software-engineer.agent.md

The Software Engineer agent implements software solutions based on provided requirements and technical designs. It executes against implementation plans created by the Architect.

Responsibilities​

  • Implementing code changes following the plan step by step.
  • Writing clean, efficient, and maintainable code.
  • Following best practices and coding standards.
  • Adhering to security considerations and quality assurance guidelines from the plan.
  • Reviewing own code to ensure it meets requirements.
  • Communicating with the Architect when ambiguities arise.

Key Behaviors​

  • Strictly follows the plan — Does not deviate unless explicitly instructed.
  • No dead code — Does not create unused functions or future-only code.
  • No unnecessary files — Focus on delivering required changes efficiently.
  • Well-documented — Includes comments and documentation for future maintainability.

Tool Access​

ToolUsage
AtlassianSearch for task requirements and related context (search only)
Context7Search API documentation, find solutions to errors, research best practices
FigmaExtract design specifications for frontend tasks
PlaywrightVerify UI implementation by interacting with the running application
Sequential ThinkingImplement complex algorithms, debug issues, plan refactoring
TerminalRun build tools, tests, linters, and scripts
File Read/Edit/SearchRead, modify, and search workspace files
VS Code CommandsExecute VS Code commands and preview in browser
Sub-agentsDelegate subtasks to specialized agents
TodoTrack implementation progress with structured checklists

Skills Loaded​

  • tsh-technical-context-discovering — Establish project conventions and patterns before implementing.
  • tsh-implementation-gap-analysing — Verify what exists vs what needs to be built.
  • tsh-codebase-analysing — Understand existing architecture for complex features.
  • tsh-implementing-frontend — Component patterns, composition, design tokens, Figma-to-code workflow.
  • tsh-implementing-forms — Schema validation, field composition, error handling, multi-step form flows.
  • tsh-writing-hooks — Custom hooks: naming, composition, stable returns, effect cleanup, testing.
  • tsh-ensuring-accessibility — WCAG 2.1 AA compliance: semantic HTML, ARIA, keyboard navigation, focus management.
  • tsh-optimizing-frontend — Code splitting, memoization, bundle size, rendering optimization, memory management.
  • tsh-ui-verifying — Tolerances and structure checklist for Figma verification.
  • tsh-sql-and-database-understanding — SQL queries, database schemas, migrations, ORM patterns.

Handoffs​

After completing implementation, the Software Engineer can hand off to:

  • Code Reviewer → /tsh-review (review implementation against the plan)
  • E2E Engineer → /tsh-implement-e2e (create E2E tests for the implemented feature)