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
console.error('[outcome] failed to persist outcome', persistError)
129
-
})
128
+
console.error("[outcome] failed to persist outcome", persistError);
129
+
});
130
130
}
131
-
}
131
+
};
132
132
```
133
133
134
134
If your store supports camelCase cleanly, standardize on camelCase end-to-end instead of mapping. The important rule is one casing per layer, not a forced snake_case database.
Copy file name to clipboardExpand all lines: .agents/skills/conductor-setup/SKILL.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Use this skill when configuring a repository for Conductor workspaces. When invo
17
17
-`references/settings-and-migration.md` for settings layers, schemas, supported repository fields, or `conductor.json` migration.
18
18
-`references/scripts-and-environment.md` for setup/run/archive scripts, shells, variables, concurrency, Spotlight, or caches.
19
19
-`references/files-layouts-and-troubleshooting.md` for Files to copy, `.worktreeinclude`, monorepos, linked repositories, MCP/privacy, or diagnosis.
20
-
Read more than one only when the task crosses those concerns.
20
+
Read more than one only when the task crosses those concerns.
21
21
3. Apply the selected reference's documented contract. Prefer team settings over machine-local configuration; preserve an existing deliberate script layout; use Conductor variables instead of hard-coded workspace paths, resources, and local ports.
22
22
4. Keep secrets and machine-specific credentials out of committed settings. Change MCP/privacy configuration only when asked or required by repository policy.
23
23
5. Validate TOML and run the narrowest relevant check for every script changed. Report when the existing setup already satisfies the requested outcome.
description: 'Create a README.md file for the project'
4
+
---
5
+
6
+
## Role
7
+
8
+
You're a senior expert software engineer with extensive experience in open source projects. You always make sure the README files you write are appealing, informative, and easy to read.
9
+
10
+
## Task
11
+
12
+
1. Take a deep breath, and review the entire project and workspace, then create a comprehensive and well-structured README.md file for the project.
13
+
2. Take inspiration from these readme files for the structure, tone and content:
3. Do not overuse emojis, and keep the readme concise and to the point.
19
+
4. Do not include sections like "LICENSE", "CONTRIBUTING", "CHANGELOG", etc. There are dedicated files for those sections.
20
+
5. Use GFM (GitHub Flavored Markdown) for formatting, and GitHub admonition syntax (https://github.com/orgs/community/discussions/16925) where appropriate.
21
+
6. If you find a logo or icon for the project, use it in the readme's header.
0 commit comments