agentboot 0.1.0

package/CONTRIBUTING.md

@@ -0,0 +1,168 @@
+# Contributing to AgentBoot
+
+AgentBoot is a community project. This document explains what we are building together,
+what belongs in the core versus a domain layer, and the quality bar for contributions.
+
+---
+
+## What is in scope
+
+### New core personas
+A persona belongs in core if it addresses a universal development concern — something
+any engineering team in any industry would benefit from. Good examples: an architecture
+reviewer, a documentation reviewer, a dependency audit persona.
+
+A persona does NOT belong in core if it assumes specific frameworks, compliance regimes,
+business domains, or organizational structures. Those belong in a domain layer.
+
+### New core traits
+Traits are behavioral building blocks. A trait belongs in core if it describes a
+reusable cognitive stance or output discipline that is domain-agnostic — the way
+`critical-thinking` or `structured-output` are. If the trait only makes sense in the
+context of a specific domain, it belongs in a domain layer instead.
+
+### Domain templates
+New domain templates under `domains/` are welcome. A domain template shows teams in
+a specific vertical (healthcare, fintech, defense, government) how to build a compliance
+layer on top of AgentBoot core without modifying core itself. Domain templates must
+be generic enough that any team in that vertical can use them as a starting point.
+They must not include real regulatory text, proprietary content, or org-specific rules.
+
+### Bug fixes
+Any defect in a persona, trait, instruction fragment, build script, sync script, or
+CI configuration is in scope.
+
+### Documentation
+Improvements to any file under `docs/`, the main `README.md`, or inline documentation
+inside trait and persona files are always welcome.
+
+---
+
+## What is NOT in scope
+
+- **Org-specific personas.** A persona built for one company's engineering standards is
+  not useful to anyone else. Fork the repo or use the `extend` field in
+  `agentboot.config.json` to keep it private.
+- **Proprietary domain content.** Do not contribute traits or personas that contain
+  internal compliance rules, internal coding standards, or references to non-public
+  specifications.
+- **Opinions about coding styles.** AgentBoot ships agnostic on tabs vs. spaces,
+  semicolons, naming conventions, etc. Personas that enforce any particular style
+  convention belong in org forks, not in core.
+- **Tool-specific integrations that are not widely applicable.** An integration with
+  a niche internal tool is not core material.
+
+---
+
+## How to propose a new persona
+
+**Issue first, then PR.** Do not open a PR for a new persona without a corresponding
+issue that has been acknowledged by a maintainer.
+
+1. Open an issue using the [Persona Request](.github/ISSUE_TEMPLATE/persona-request.md)
+   template.
+2. Describe the use case clearly. What problem does this persona solve? What does a
+   team look like before and after deploying it?
+3. List the traits it would compose. If it requires a new trait, say so and explain why
+   existing traits are insufficient.
+4. Provide an example invocation — a realistic prompt a developer would give it and
+   the output they would expect.
+5. Explain why this belongs in core rather than a domain extension (see scope rules above).
+6. Wait for maintainer acknowledgment before writing code. This prevents wasted effort
+   on proposals that don't fit the project direction.
+
+---
+
+## Trait design principles
+
+Traits are the foundation of AgentBoot's composability. Bad traits make the whole system
+worse. Good traits follow these principles:
+
+**Generic, not specific.** A trait describes a cognitive stance or output discipline, not
+a checklist of domain rules. `critical-thinking` is a stance. "Check that HIPAA audit
+logs are present" is a domain rule and belongs in a domain layer.
+
+**Composable, not monolithic.** A trait does one thing. If you are writing a trait that
+covers two unrelated concerns, split it. Traits that try to do everything end up doing
+nothing well.
+
+**No domain assumptions.** A trait must not assume any particular framework, language,
+industry, compliance regime, or organizational structure. If your trait works for a
+Spring Boot API team but not for a React frontend team, it is not a core trait.
+
+**Configurable where it matters.** Look at `critical-thinking` as the model: the trait
+defines the behavior at each weight level, and the persona that composes it sets the
+weight. Traits that have meaningful axes of variation should expose them in frontmatter
+rather than hardcoding a single behavior.
+
+**Negative space matters.** Every trait must include a "what not to do" section. Personas
+that lack this section tend to produce output that is exhaustive but not useful.
+
+---
+
+## Persona quality bar
+
+A persona is not ready to merge until it meets all of these requirements.
+
+**Frontmatter.** Every persona file must include a YAML frontmatter block with:
+- `id`: the slash-command identifier (e.g., `review-code`)
+- `name`: human-readable display name
+- `version`: semantic version starting at `1.0.0`
+- `traits`: list of trait IDs with weights where applicable
+- `scope`: one of `file`, `pr`, `repo`, `session`
+- `output_format`: one of `structured`, `prose`, or `mixed`
+
+**System prompt.** The persona must have a clear, complete system prompt that defines
+its role, its operating assumptions, and its mandate. The system prompt should not be
+a list of rules — it should read like a job description.
+
+**Output format specification.** The persona must specify exactly what its output looks
+like. If the output is structured, show the schema. If it is prose, describe the
+sections. Ambiguous output specs lead to inconsistent persona behavior across models.
+
+**What-not-to-do section.** Every persona must have a section describing anti-patterns —
+things the persona must not do, tempting behaviors that would make it less useful, and
+scope boundaries it must not cross.
+
+**Example.** Every new persona must include at least one worked example: a realistic
+input and the expected output. This is the primary way reviewers verify that the persona
+does what it claims.
+
+---
+
+## Contributor License Agreement
+
+First-time contributors must sign our CLA. When you open your first pull request,
+the CLA bot will post a comment with instructions. This is a one-time process that
+takes about 30 seconds — you sign by posting a comment on the PR.
+
+The CLA grants the project maintainers the right to relicense your contributions if
+needed for the long-term sustainability of the project. Your contributions remain
+attributed to you. The full agreement is in [`CLA.md`](CLA.md).
+
+---
+
+## PR checklist
+
+Before opening a PR, verify:
+
+- [ ] `npm run validate` passes with no errors
+- [ ] `npm run build` passes with no errors
+- [ ] `PERSONAS.md` is updated if you added or changed a persona
+- [ ] `README.md` is updated if the change affects the project overview
+- [ ] An example is included if you added a new persona
+- [ ] The trait design principles are satisfied if you added a new trait
+- [ ] The persona quality bar is met if you added a new persona
+- [ ] The issue number is referenced in the PR description
+
+---
+
+## Code of conduct
+
+AgentBoot follows the [Contributor Covenant](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)
+version 2.1. By contributing, you agree to uphold these standards. Report violations
+to the project maintainers.
+
+---
+
+*Thank you for making AgentBoot better.*

package/LICENSE

@@ -0,0 +1,191 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by the Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding any notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Michel Saavedra
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+AgentBoot
+Copyright 2026 Michel Saavedra
+
+Licensed under the Apache License, Version 2.0.

package/PERSONAS.md

@@ -0,0 +1,156 @@
+# AgentBoot Persona Registry
+
+This file is the authoritative registry of all personas shipped with AgentBoot core.
+It is generated automatically by `npm run build` — do not edit it manually.
+If this file is out of date, run `npm run build` and commit the result.
+
+---
+
+## V1 Personas
+
+| Persona | ID | Invocation | Scope | Traits Composed | IDE Available |
+|---|---|---|---|---|---|
+| Code Reviewer | `code-reviewer` | `/review-code` | PR / file | critical-thinking (MEDIUM), structured-output, source-citation, confidence-signaling | Yes |
+| Security Reviewer | `security-reviewer` | `/review-security` | PR / file | critical-thinking (HIGH), structured-output, source-citation, confidence-signaling, audit-trail | Yes |
+| Test Generator | `test-generator` | `/gen-tests` | file | schema-awareness, structured-output, source-citation | Yes |
+| Test Data Expert | `test-data-expert` | `/gen-testdata` | session | schema-awareness, structured-output | Yes |
+
+### Code Reviewer
+
+Performs code review against your team's standards. Produces severity-tiered findings
+(CRITICAL / WARN / INFO) with source citations. Uses `critical-thinking: MEDIUM` —
+flags clear defects and significant design concerns without opining on style preferences.
+
+**Typical invocation:**
+```
+/review-code
+```
+or on a specific file:
+```
+/review-code src/services/payment-service.ts
+```
+
+**Output format:** Structured findings list. Each finding includes: severity, location
+(file + line), description, citation, and recommendation.
+
+---
+
+### Security Reviewer
+
+Security-focused code review. Uses `critical-thinking: HIGH` — treats absence of
+evidence as a gap, surfaces worst-case scenarios first, never softens findings to
+avoid friction. Covers: authentication, authorization, input validation, cryptographic
+usage, secret handling, injection risks, and dependency vulnerabilities.
+
+**Typical invocation:**
+```
+/review-security
+```
+or targeted:
+```
+/review-security src/auth/
+```
+
+**Output format:** Structured findings list. Security findings include an additional
+`cvss_estimate` field (LOW / MEDIUM / HIGH / CRITICAL) and an `exploitability` note.
+
+---
+
+### Test Generator
+
+Generates unit and integration tests from function signatures, class definitions, or
+module exports. Produces tests in the testing framework already used in the repo
+(detected from `package.json` devDependencies and existing test files). Covers: happy
+path, boundary conditions, error cases, and null/undefined handling.
+
+**Typical invocation:**
+```
+/gen-tests src/services/user-service.ts
+```
+
+**Output format:** Ready-to-run test file(s) following the repo's existing test
+conventions. Includes a brief explanation of what each test covers and why.
+
+---
+
+### Test Data Expert
+
+Generates realistic, schema-consistent synthetic test data. Reads the data model from
+TypeScript types, Zod schemas, or database schema files and produces data that is
+structurally valid, type-correct, and diverse enough to exercise edge cases.
+
+**Typical invocation:**
+```
+/gen-testdata src/domains/user/user.types.ts
+```
+
+**Output format:** TypeScript constant declarations, JSON fixtures, or SQL INSERT
+statements (detected from context). Each output includes a comment explaining any
+domain assumptions made.
+
+---
+
+## IDE Availability
+
+All V1 personas are available via Claude Code slash commands (the primary interface).
+All personas that produce structured output also work in editor integrated mode —
+when invoked from within an open file, they automatically scope to the visible file
+context.
+
+For GitHub Copilot and Cursor compatibility, see the note about agentskills.io in
+[`README.md`](README.md). Personas compiled from AgentBoot follow the SKILL.md standard
+and work in any agentskills.io-compatible tool.
+
+---
+
+## V1 Core Traits
+
+| Trait | ID | Configurable | Used By |
+|---|---|---|---|
+| Critical Thinking | `critical-thinking` | Yes (HIGH/MEDIUM/LOW) | code-reviewer, security-reviewer |
+| Structured Output | `structured-output` | No | all V1 personas |
+| Source Citation | `source-citation` | No | code-reviewer, security-reviewer, test-generator |
+| Confidence Signaling | `confidence-signaling` | No | code-reviewer, security-reviewer |
+| Audit Trail | `audit-trail` | No | security-reviewer |
+| Schema Awareness | `schema-awareness` | No | test-generator, test-data-expert |
+
+---
+
+## Personas in the growth pipeline
+
+The following personas are under consideration for V2. None are committed or scheduled.
+If you want to work on one, open an issue using the
+[Persona Request](.github/ISSUE_TEMPLATE/persona-request.md) template.
+
+- **Architecture Reviewer** — Reviews structural decisions, dependency direction, and
+  bounded context violations. Candidate scope: PR / ADR file.
+- **Documentation Reviewer** — Checks that public APIs, complex functions, and
+  architectural decisions are documented adequately. Candidate scope: PR / file.
+- **Dependency Auditor** — Audits `package.json` / `pom.xml` / `go.mod` for outdated,
+  vulnerable, or license-incompatible dependencies. Candidate scope: session.
+- **Incident Analyst** — Given a log dump or error trace, identifies root cause, blast
+  radius, and remediation path. Candidate scope: session.
+- **Database Reviewer** — Reviews schema migrations for safety, reversibility, and
+  performance risks. Candidate scope: PR / migration file.
+
+---
+
+## How to contribute a persona
+
+1. Read [`docs/concepts.md`](docs/concepts.md) to understand what a persona is and how
+   it composes traits.
+2. Read [`CONTRIBUTING.md`](CONTRIBUTING.md) for the quality bar and the issue-first policy.
+3. Open a [Persona Request](.github/ISSUE_TEMPLATE/persona-request.md) issue.
+4. Wait for maintainer acknowledgment before writing code.
+
+The quality bar for a merged persona:
+- Complete SKILL.md frontmatter (id, name, version, traits, scope, output_format)
+- Clear system prompt that reads like a job description
+- Explicit output format specification
+- What-not-to-do section
+- At least one worked example
+
+---
+
+*Generated by AgentBoot build. Do not edit manually.*
+*Last updated: 2026-03-17*