claude-teammate 0.1.27 → 0.1.28

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +3 -0
  2. package/package.json +1 -1
  3. package/src/claude.js +1 -1
package/README.md CHANGED
@@ -162,6 +162,9 @@ Yes. Each epic is scoped to its own Jira domain and workspace, and can map to on
162
162
  **Does it understand the codebase or just generate generic code?**
163
163
  It reads the actual repository before writing anything - structure, conventions, existing patterns. The plan it proposes is specific to your code, not a template.
164
164
 
165
+ **Can I use Claude skills or MCP, and does it respect `CLAUDE.md`?**
166
+ Yes. Claude skills, configured MCP servers, and repo instructions in `CLAUDE.md` are available and respected just like they are in a normal Claude-driven workflow. Playwright MCP is built in and enabled by default so challenging frontend tasks can be verified in-browser.
167
+
165
168
  <br/>
166
169
 
167
170
  ## Roadmap
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "claude-teammate",
3
- "version": "0.1.27",
3
+ "version": "0.1.28",
4
4
  "description": "CLI bootstrapper for Claude Teammate.",
5
5
  "license": "MIT",
6
6
  "type": "module",
package/src/claude.js CHANGED
@@ -1074,7 +1074,7 @@ Instructions:
1074
1074
  - Implement the plan described in the pull request body.
1075
1075
  - Smart quotes and em/en dashes are not allowed. Use: smart quotes -> ", em/en dashes -> -.
1076
1076
  - If the latest human PR comment requests a change or reports a problem, address that feedback as part of this implementation run.
1077
- - If this involves frontend behavior, infer how to start the app from the repository code, launch it locally, and verify the implementation with Playwright MCP.
1077
+ - If this involves challenging frontend fixes/implementations, infer how to start the app from the repository code, launch it locally, and verify the implementation with Playwright MCP.
1078
1078
  - Do not commit or push; leave modified files in the working tree.
1079
1079
  - Return summary as 1-2 sentences suitable to post directly as a PR comment.
1080
1080
  - Return epic_facts and epic_guardrails only for reusable non-obvious repo or epic knowledge. Use epic_facts for durable factual notes such as build commands or stable repo behavior. Leave them empty when there is nothing worth remembering.