
Avdo Redzepagic
Problem solving - Handling bugs
Depending on the type of bugs there might be a different approach to the issue at hand. We have separated the most common bug types into these categories so the developer can further strategise the approach for resolving either one of these

repo-root/
├── CLAUDE.md # our rules + auto-applies AI-DLC + ClickUp ticket gate
├── AGENTS.md # same gates for other agents (client)
├── .aidlc-agent/
│ ├── core-workflow.md # upstream AWS orchestration rules
│ └── agent-config.yml # rule dir, output dirs, enabled extensions
├── .aidlc-rule-details/ # upstream stage rules: common/ inception/ construction/ extensions/
├── .claude/
│ ├── agents/aidlc-agent.md # the orchestrator subagent
│ ├── agents/browser-qa.md # browser verification subagent (client)
│ ├── skills/clickup-dev-workflow/
│ ├── skills/browser-verification/
│ ├── hooks/require-browser-verification.mjs
│ └── settings.json # PreToolUse hook wiring
├── .mcp.json # Playwright MCP (client)
├── coding-guidelines/ # our standards, one file per topic
└── aidlc-docs/ # generated: audit.md, aidlc-state.md, plans, requirements
AI-DLC in Practice
An AI coding agent is only as good as the process around it. How Sunray uses AWS AI-DLC, coding guidelines, a ClickUp ticket workflow and MCP servers to ship production code with Claude Code.

Almir Bećirović