You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/roles.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ This file defines the runnable AI role workflow for DevLog work.
6
6
7
7
It is not background documentation. Use it to split work across AI models, pass task packets between roles, and decide which review or verification gates must run before completion.
8
8
9
-
Use `AGENT_WORKFLOWS.md` for task-specific runbooks that combine these roles into executable workflows.
9
+
Use `.agents/workflows.md` for task-specific runbooks that combine these roles into executable workflows.
10
10
11
11
`AGENTS.md` remains the canonical repository rule file. If this file conflicts with `AGENTS.md`, follow `AGENTS.md`.
12
12
@@ -18,7 +18,7 @@ Use `AGENT_WORKFLOWS.md` for task-specific runbooks that combine these roles int
18
18
- The main agent owns integration, final diff inspection, and the final user report.
19
19
- Build-only verification is allowed. Do not run, launch, install, boot, or open the app or Simulator unless the user explicitly requests it in the current turn.
20
20
- Keep generated Xcode workspace/project and `Package.resolved` churn out of source control unless an approved dependency-lock policy requires it.
21
-
- Keep AI workflow documents at the repository root, such as `AGENT_ROLES.md`. Do not put them under `docs/`.
21
+
- Keep AI workflow and rule documents under `.agents/`. Do not put them under `docs/`.
22
22
23
23
## Model assignment
24
24
@@ -97,7 +97,7 @@ Use this sequence for non-trivial AI-assisted work.
97
97
98
98
Read-only roles can run in parallel when they do not depend on the same unfinished output. Editing roles should run sequentially unless their assigned files and ownership boundaries are disjoint.
99
99
100
-
For full issue, implementation, review, CI, and docs-only runbooks, use `AGENT_WORKFLOWS.md`.
100
+
For full issue, implementation, review, CI, and docs-only runbooks, use `.agents/workflows.md`.
101
101
102
102
## Task packet
103
103
@@ -128,7 +128,7 @@ Use this template when assigning a `Lightweight` or `Fast` role through its conf
128
128
```md
129
129
You are the `<Role Name>` for the DevLog iOS repository.
130
130
131
-
Read `AGENTS.md` first. Then read `AGENT_ROLES.md` and follow the `<Role Name>` section.
131
+
Read `AGENTS.md` first. Then read `.agents/roles.md` and follow the `<Role Name>` section.
132
132
133
133
Assigned model tier: `<Lightweight | Fast>`
134
134
Custom agent: `<configured custom agent name>`
@@ -153,7 +153,7 @@ The receiving model must start by identifying its active role and must end with
153
153
| --- | --- | --- |
154
154
| Issue planning | Planner | Add GitHub/CI Analyst when live issue or PR state is the source of truth. |
155
155
| Swift implementation | Planner, Implementer, Code Reviewer, Verification Runner | Add Architecture Watcher when boundary or dependency risk exists. |
156
-
| Module, DI, SDK, Widget, StorePattern, or architecture docs | Planner, Architecture Watcher, Implementer, Code Reviewer, Verification Runner | Architecture Watcher must read `AGENTS.md`, `.gemini/styleguide.md`, `README.md`, and `.hermes/skills/devlog-architecture-harness/references/devlog-architecture-flow.md`. |
156
+
| Module, DI, SDK, Widget, StorePattern, or architecture docs | Planner, Architecture Watcher, Implementer, Code Reviewer, Verification Runner | Architecture Watcher must read `AGENTS.md`, `.gemini/styleguide.md`, `README.md`, and `.agents/rules/architecture.md`. |
Copy file name to clipboardExpand all lines: .agents/rules/architecture.md
+42-6Lines changed: 42 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,52 @@
1
-
# DevLog Architecture Flow
1
+
# DevLog Architecture Rules
2
2
3
3
## Purpose
4
4
5
-
This reference defines the DevLog-specific harness flow for AI-assisted architecture work.
5
+
This reference defines the DevLog-specific flow and boundaries for AI-assisted architecture work.
6
6
7
7
The goal is not to make the AI decide more architecture policy. The goal is to make the AI stop before it makes project-specific architecture decisions that should be confirmed by the user.
8
8
9
-
Use this reference with `AGENTS.md`and `.hermes/skills/devlog-architecture-harness/SKILL.md`.
9
+
Use this reference with `AGENTS.md`, `.agents/rules/general.md`, and `.agents/roles.md`.
10
10
11
11
This repository is a Tuist-generated, workspace-based modular iOS app. There is no root `Package.swift`; module projects are generated from `Workspace.swift` and each module's `Project.swift`.
12
12
13
-
## High-level harness flow
13
+
## When to use
14
+
15
+
Read this file before work that changes any of these areas:
16
+
17
+
- Module boundaries or file ownership across `Application/*` and `Widget/*` targets.
18
+
- Swift imports or Tuist target dependencies.
19
+
- DI assembler wiring or same-layer dependency injection.
20
+
- Repository, service, store, or use case contracts.
21
+
- Firebase, social login, network, link metadata, notification, or WidgetKit dependency placement.
22
+
- Widget snapshot, App Group, or widget deep-link data flow.
23
+
- Architecture diagrams, README architecture text, or PR architecture explanations.
24
+
25
+
Before editing, also read `.gemini/styleguide.md` and `README.md`. Read `.agents/rules/project-workflows.md` when the task involves PR review, commits, Xcode project files, CI, widgets, Store reducers, localization, release, or build tooling.
26
+
27
+
Then inspect the concrete files, Swift imports, and Tuist target dependencies related to the requested change. Do not rely on layer names alone.
28
+
29
+
## Mandatory flow
30
+
31
+
1. Identify the changed layer and owning target before editing.
32
+
2. Inspect the current Swift import direction and Xcode target/framework dependency before deciding.
33
+
3. Classify the change as mechanical, architectural, or ambiguous.
34
+
4. Stop and ask the user before editing when the architecture boundary is ambiguous.
35
+
5. Keep the diff limited to the requested architecture scope.
36
+
6. Follow `.agents/rules/project-workflows.md` for verification after Swift or iOS project changes.
37
+
7. Report the changed files, architecture decision, verification result, and unresolved user decisions.
38
+
39
+
## Safe mechanical changes
40
+
41
+
These may proceed after inspection when they do not change architecture meaning:
42
+
43
+
- Removing unused imports.
44
+
- Updating import statements after an already-approved file move.
45
+
- Fixing access control needed by an already-approved module boundary.
46
+
- Updating tests to match an already-approved public contract.
47
+
- Editing docs to reflect the current verified architecture.
48
+
49
+
## High-level architecture flow
14
50
15
51
```mermaid
16
52
flowchart TD
@@ -309,7 +345,7 @@ Widget UI should consume snapshot data. It should not fetch app services or doma
309
345
flowchart TD
310
346
Changed["Files changed"]
311
347
Swift{"Swift/iOS project code changed?"}
312
-
Docs{"Docs or harness only?"}
348
+
Docs{"Docs or architecture rules only?"}
313
349
Xcode["Build with Xcode Local MCP"]
314
350
Diff["Inspect git diff scope"]
315
351
NoBuild["No iOS build required"]
@@ -346,4 +382,4 @@ Before editing architecture code, the AI should be able to answer these question
346
382
- Swift logic was preserved unless explicitly approved.
347
383
- Diff scope was checked.
348
384
- Xcode Local MCP build was used for Swift/iOS code changes.
349
-
- Docs-only or harness-only changes were reported as such, without claiming app build verification.
385
+
- Docs-only or architecture-rule-only changes were reported as such, without claiming app build verification.
Copy file name to clipboardExpand all lines: .agents/rules/project-workflows.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@ This reference holds DevLog-specific working rules that should live with the pro
4
4
5
5
## Canonical source
6
6
7
-
- Treat this repository's `AGENTS.md` and `.hermes/skills/devlog-architecture-harness` as the canonical DevLog working rules.
7
+
- Treat this repository's `AGENTS.md` and routed `.agents/` documents as the canonical DevLog working rules.
8
8
- Use global memory only as historical context. If global memory conflicts with this repository, follow the repository.
9
9
- Before changing architecture rules, update the repository-local rules first.
10
10
11
11
## Verification
12
12
13
-
-Follow `AGENTS.md` for the canonical lint and build verification policy.
13
+
-Treat this section as the canonical lint and build verification policy routed by `AGENTS.md`.
14
14
- Run Homebrew SwiftLint (`swiftlint`) on changed Swift files.
15
15
- Lint production Swift files with the applicable source `.swiftlint.yml` config.
16
16
- Lint test Swift files with `.swiftlint-tests.yml` or the module `Tests/.swiftlint.yml` that inherits from it. Do not use the root production config for tests.
@@ -43,6 +43,11 @@ This reference holds DevLog-specific working rules that should live with the pro
43
43
44
44
## Commit guidance
45
45
46
+
- Commit messages must start with a short prefix used by recent local commits, such as `feat`, `fix`, `refactor`, `chore`, `test`, `docs`, `ui`, or `rollback`.
47
+
- Write commit message prose in Korean.
48
+
- Keep implementation names such as `ToastPresenter`, `toastHost`, `MainView`, `Presentation`, file paths, commands, branch names, and commit hashes in their original form.
49
+
- Do not translate implementation names into Korean unless the user explicitly asks for a user-facing Korean label.
50
+
- Do not write a commit message body.
46
51
- If the user says they will commit or asks only for a commit message, provide commit-message guidance instead of committing.
47
52
- Before proposing a commit message, inspect the actual diff and recent `git log`.
48
53
- When recent history contains GitHub merge commits, do not infer commit-message style from merge subjects such as `[#123] ... (#456)`. Open the merge commit with `git show --no-patch --format=full <merge-commit>` and use the individual commit messages in the body, or inspect nearby non-merge commits.
Copy file name to clipboardExpand all lines: .agents/workflows.md
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,20 +4,20 @@
4
4
5
5
This file defines executable AI workflows for DevLog work.
6
6
7
-
Use this after reading `AGENTS.md` and `AGENT_ROLES.md`. `AGENT_ROLES.md` defines what each role may do. This file defines how to combine those roles for common project tasks.
7
+
Use this after reading `AGENTS.md` and `.agents/roles.md`. `.agents/roles.md` defines what each role may do. This file defines how to combine those roles for common project tasks.
8
8
9
9
If this file conflicts with `AGENTS.md`, follow `AGENTS.md`.
10
10
11
11
## Main-agent protocol
12
12
13
13
The main agent must run every workflow with this protocol.
14
14
15
-
1. Read `AGENTS.md`, then `AGENT_ROLES.md`, then this file.
15
+
1. Read `AGENTS.md`, then `.agents/roles.md`, then this file.
16
16
2. Select one workflow from this file.
17
17
3. Create the task packet.
18
18
4. Assign only the roles required by the selected workflow.
19
-
5. Assign each role a model tier from `AGENT_ROLES.md`.
20
-
6. Keep `Primary` roles with the active main agent, and dispatch every `Lightweight` or `Fast` role through the custom agent mapped in `AGENT_ROLES.md`.
19
+
5. Assign each role a model tier from `.agents/roles.md`.
20
+
6. Keep `Primary` roles with the active main agent, and dispatch every `Lightweight` or `Fast` role through the custom agent mapped in `.agents/roles.md`.
21
21
7. Dispatch read-only `Lightweight` or `Fast` roles in parallel only when they do not depend on unfinished edits.
22
22
8. Do not complete a required `Lightweight` or `Fast` role directly in `Primary`, including when the dispatch tool would inherit the active `Primary` model.
23
23
9. Keep `Primary` editing roles sequential unless the files and ownership boundaries are disjoint.
@@ -50,7 +50,7 @@ Stop and ask the user before editing when:
Copy file name to clipboardExpand all lines: .codex/agents/documentation_writer.toml
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,9 @@ model = "gpt-5.3-codex-spark"
4
4
model_reasoning_effort = "medium"
5
5
sandbox_mode = "workspace-write"
6
6
developer_instructions = """
7
-
Read AGENTS.md and AGENT_ROLES.md before drafting.
8
-
Act only as the Documentation Writer defined in AGENT_ROLES.md.
7
+
Read AGENTS.md and .agents/roles.md before drafting.
8
+
Act only as the Documentation Writer defined in .agents/roles.md.
9
9
Match repository templates, actual diffs, live issue or PR state, and the requested Korean wording rules.
10
10
Edit only documentation files named in the task packet. Do not edit app code or create GitHub content unless the task packet explicitly authorizes that write action.
11
-
Return exactly the Documentation Result format from AGENT_ROLES.md unless the task packet requests direct Markdown draft output.
11
+
Return exactly the Documentation Result format from .agents/roles.md unless the task packet requests direct Markdown draft output.
0 commit comments