Skip to content
Back to search

francis-ai-coworking

MarketplaceWorks with Claude CodeGitHub

Claude Code plugin: one standard and a doctor for spec-driven projects

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 20 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/dangthinh104/francis-ai-coworking with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/dangthinh104/francis-ai-coworking'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dangthinh104--francis-ai-coworking/badge.svg)](/listings/dangthinh104--francis-ai-coworking)

HTML

<a href="/listings/dangthinh104--francis-ai-coworking"><img src="/api/listings/dangthinh104--francis-ai-coworking/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add dangthinh104/francis-ai-coworking
/plugin install francis-kit@francis-ai-coworking

Or let the scaffold write the keys into a project's `.claude/settings.json`, so every collaborator gets the plugin:

{
  "extraKnownMarketplaces": {
    "francis-ai-coworking": { "source": { "source": "github", "repo": "dangthinh104/francis-ai-coworking" } }
  },
  "enabledPlugins": { "francis-kit@francis-ai-coworking": true }
}

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "francis-ai-coworking",
  3. "owner": { "name": "Francis Dang", "url": "https://francisdang.com" },
  4. "metadata": {
  5. "description": "Shared Claude Code skills and agents for Francis's Spec Kit projects."
  6. },
  7. "plugins": [
  8. {
  9. "name": "francis-kit",
  10. "source": "./plugins/francis-kit",
  11. "description": "The francis-kit standard for spec-driven projects: one layout, a doctor that checks it, and the loop from spec to closed feature."
  12. }
  13. ]
  14. }
README.md · README · 161 lines
  1. # francis-ai-coworking
  2. A Claude Code plugin, `francis-kit`, for building software with Claude across several projects. It gives every project the same layout and the same way of working, and it ships a doctor that checks a project against that layout.
  3. The kit is built on spec-driven development:
  4. - A change of behaviour starts as a short spec, about 3 to 12 requirements.
  5. - Only a person approves a spec.
  6. - A feature moves through `Draft → Approved → Built → Released → Closed`. Once closed, it is merged into a living spec of what the system does today.
  7. What changed in each version, and what can turn a gate red when you move to it: [`CHANGELOG.md`](CHANGELOG.md).
  8. The kit grew out of four real projects, and each rule in it comes from a mistake an agent made in one of them.
  9. It relies on three things it does not ship:
  10. - [Claude Code](https://claude.com/claude-code).
  11. - [Spec Kit](https://github.com/github/spec-kit), whose commands write `plan.md` and `tasks.md`.
  12. - Python 3.9 or newer, with git and PyYAML, for the scripts.
  13. One more skill is optional: [archify](https://github.com/tt-a1i/archify), which draws a project's diagrams for `map-project`. Install it on its own. Without it, a session asked for a diagram says so and stops. Checking a diagram (`cite_refs.py`) needs only the kit.
  14. ## Install
  15. In Claude Code:
  16. ```
  17. /plugin marketplace add dangthinh104/francis-ai-coworking
  18. /plugin install francis-kit@francis-ai-coworking
  19. ```
  20. Or let the scaffold write the keys into a project's `.claude/settings.json`, so every collaborator gets the plugin:
  21. ```json
  22. {
  23. "extraKnownMarketplaces": {
  24. "francis-ai-coworking": { "source": { "source": "github", "repo": "dangthinh104/francis-ai-coworking" } }
  25. },
  26. "enabledPlugins": { "francis-kit@francis-ai-coworking": true }
  27. }
  28. ```
  29. ## Updates
  30. Claude Code does not update a plugin from this marketplace by itself until you turn that on: auto-update is off by default for third-party marketplaces.
  31. - **Turn on auto-update:** run `/plugin`, open the **Marketplaces** tab, select `francis-ai-coworking`, and switch auto-update on. A new version is fetched in the background, and loads at your next launch or after `/reload-plugins`.
  32. - **Update now:** run `claude plugin marketplace update francis-ai-coworking`, then `claude plugin update francis-kit@francis-ai-coworking`, then start a new session.
  33. - **Be told of a release:** on GitHub, use **Watch → Custom → Releases** for this repository. Each version has a release page, and its section in [`CHANGELOG.md`](CHANGELOG.md) says what can turn red when you move.
  34. A project's gate does not follow the plugin: it checks out the kit at the tag it pins, and moves only when you write the gate again (`kit_scaffold.py --repo . --gate`).
  35. ## Start
  36. - **A new project:** ask Claude to run the `kit-init` skill.
  37. - **A project that already has its own specs, docs or process:** ask for `kit-adopt`. It measures the gaps first, records each gap it cannot close yet as debt with the step that removes it, and closes the gaps one small pull request at a time.
  38. - **At the start of any session:** use the `flow` skill. It says which stage the work is at and what proves that stage is finished.
  39. By hand:
  40. ```bash
  41. K=<this repo>/plugins/francis-kit/skills/kit-init/scripts
  42. python3 $K/kit_scaffold.py --repo . --dry-run # what would be created
  43. python3 $K/kit_scaffold.py --repo . # profiles: laravel-vue, python, generic
  44. python3 $K/kit_doctor.py --repo . # PASS, GAP, DEBT or SKIP for each rule
  45. python3 $K/kit_gate.py --repo . # every check, and one verdict line
  46. ```
  47. On Windows, where `python3` is often not found, use `python`.
  48. ## The standard in one screen
  49. The full text, with rules S01 to S19, is in [`plugins/francis-kit/STANDARD.md`](plugins/francis-kit/STANDARD.md).
  50. ```
  51. CLAUDE.md short: hazards, rules, where to read next
  52. .claude/kit.yml facts about this project, nothing else
  53. .claude/skills/<domain>/SKILL.md home of the rules for one domain
  54. .specify/memory/constitution.md non-negotiable principles
  55. specs/NNN-slug/spec.md plan.md tasks.md history.md
  56. specs/_living/<capability>/spec.md what the system does today
  57. docs/ARCHITECTURE.md the map, 200 lines at most
  58. docs/diagrams/map.refs.json anchored citations for the map
  59. .github/workflows/kit-gate.yml the gate, on pull requests
  60. .githooks/pre-push or the gate at each push
  61. ```
  62. Work comes in three lanes:
  63. - **Fix:** a fix that does not change behaviour needs no spec, only a ticked line under `## Fixes` in the feature that owns the behaviour.
  64. - **Spec:** a change of behaviour is one feature.
  65. - **Split:** anything larger is split into at most five features behind one page of intent.
  66. ## What is inside
  67. | Type | Name | Purpose |
  68. |---|---|---|
  69. | Skill | `flow` | The loop, and how to find the current stage |
  70. | Skill | `kit-init` | A new project on the standard |
  71. | Skill | `kit-adopt` | An existing project onto the standard, gap by gap |
  72. | Skill | `write-spec` | A request into a spec: the lane, one round of questions, a lint, stop at Draft |
  73. | Skill | `map-project` | An architecture map whose citations can be checked |
  74. | Skill | `close-feature` | After a release: merge the spec into the living spec, trim comments |
  75. | Skill | `find-cause` | Before a fix: show the failure, state the cause with its evidence, stop after three failed fixes |
  76. | Skill | `code-shape` | Checkable rules for simple code |
  77. | Skill | `comment-discipline` | Five rules for comments, and citations of requirements in code |
  78. | Skill | `security` | Input, permissions, secrets, files; adding a package that really exists |
  79. | Skill | `ui-copy` | Words a user reads, in the user's language |
  80. | Skill | `design-direction` | A visual direction before interface code |
  81. | Skill | `shrink-claude-md` | A long `CLAUDE.md` into a short one, block by block, approved by the owner, then verified |
  82. | Skill | `cleanup` | Remove clutter in a scoped area |
  83. | Agent | `spec-writer` | Drafts one spec; never approves |
  84. | Agent | `spec-reviewer` | Reads a spec cold before a person approves it |
  85. | Agent | `project-mapper` | Writes the map in a clean context |
  86. | Agent | `feature-closer` | Closes a released feature in a clean context |
  87. | Agent | `repo-janitor` | Cleans one scoped area |
  88. ## The gate in each project
  89. A project chooses one gate, and the scaffold writes it:
  90. - **A workflow** (`.github/workflows/kit-gate.yml`), on GitHub-hosted runners or on a runner of the project's own.
  91. - **A `pre-push` hook** (`.githooks/pre-push`), for a project where no runner can run it.
  92. Both check out this repository at the tag of the kit version that wrote them, and run `kit_gate.py`. A project moves to a newer kit by running `kit_scaffold.py --repo . --gate` again with that version. The doctor reports a gate that pins an older kit as a gap until it moves.
  93. Neither gate needs a secret: the kit is public. The workflow does not start on pull requests from a fork or from Dependabot.
  94. The gate checks out the kit by its tag. A tag can be moved, so the tags of this repository are never moved: a fix is a new version.
  95. When a project moves to a newer kit, it writes its gate again before it records a second deviation on a rule. The gate runs the doctor of the version it pins, and an older doctor reports that entry as listed twice.
  96. ## Known limits
  97. - The doctor checks structure, not truth. It cannot tell whether a `Released` feature really shipped, or whether the living spec is right. Review and the `feature-closer` agent cover that.
  98. - The gate does not run a project's tests.
  99. - S19 checks that the tests run on pull requests, and it does this by reading the workflow files under `.github/workflows` word for word. A project whose CI is elsewhere records S19 as debt.
  100. - The hook guards the author's clone, not the release: `git push --no-verify` skips it, and a merge in GitHub's web interface is not judged.
  101. - The plugin's hook raises a permission prompt before an Edit or Write adds an `Approved` Status line to a `specs/NNN-*/spec.md` that did not hold one. The prompt is a confirmation, not the approval: the approval is still the person's yes to the question that names the feature, its number of requirements and that no open question is left (`STANDARD.md`, Status). The hook asks and never refuses or allows; where it fails while checking a spec, it asks and names the error.
  102. - What the hook does not see. With no Python, or a plugin root that does not lead to `hooks/guard.py`, nothing is checked and nothing says so. A spec written through Bash or PowerShell (`sed`, `echo >`, `Set-Content`) is not seen, nor one written by NotebookEdit. MultiEdit is not matched: in a Claude Code version that still has it, it is a way around the hook. The path rule reads the path as text, so an alias of a spec's path is not recognised and raises no prompt: on Windows a trailing dot (`spec.md.`), a stream name (`spec.md::$DATA`), an 8.3 short name (`SPEC~1.MD`); on any system a symlink (on Windows also a junction) that leads to the spec. A line the person writes in their own editor raises no prompt, and that line is the approval. A subagent's write is asked like any other, because the input does not say it comes from a subagent; the prompt's reason says it is not an approval. A Status line the kit does not read (indented, or in front matter, a closed fenced block, a code span or an HTML comment) raises no prompt. On Windows without Git Bash, what happens to the hook's command is unverified. In `dontAsk` mode Claude Code refuses whatever would prompt, so the prompt becomes a refusal; what `bypassPermissions`, `acceptEdits` and plan mode do with it is unverified, and a `deny` rule in the settings still wins. The hook cannot be turned off on its own: disabling the plugin, or setting `disableAllHooks`, turns it off. It sets no timeout, and what Claude Code's default timeout does to it is unverified.
  103. - The other rules that hold within a session are in the skills, not in a hook. No gate can check them.
  104. - The test suite needs the full git history. On Windows without the symlink privilege, the tests that create a symlink are skipped one by one. A run that skipped more tests than it ran exits 1.
  105. ## Tests
  106. ```bash
  107. pip install -r requirements-dev.txt
  108. python -m pytest tests -q
  109. ```
  110. `sh local-check.sh` runs the suite here, and on Linux with Python 3.9 and 3.12 in Docker.
  111. The kit is developed in a private repository. This copy is published at each release, without history and without the specs and fixtures that came from private projects. Tests that need those files are left out of this copy.
  112. ## Author
  113. Francis Dang, [francisdang.com](https://francisdang.com).
  114. ## License
  115. MIT. See [`LICENSE`](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.