@groupby/ai-dev 0.2.1 → 0.3.0

package/skills/skills/library/frontend-design/LICENSE.txt

@@ -1,177 +0,0 @@
-
-                                 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 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 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 those 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

package/skills/skills/library/frontend-design/SKILL.md

@@ -1,42 +0,0 @@
----
-name: frontend-design
-description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
-license: Complete terms in LICENSE.txt
----
-
-This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.
-
-The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints.
-
-## Design Thinking
-
-Before coding, understand the context and commit to a BOLD aesthetic direction:
-- **Purpose**: What problem does this interface solve? Who uses it?
-- **Tone**: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
-- **Constraints**: Technical requirements (framework, performance, accessibility).
-- **Differentiation**: What makes this UNFORGETTABLE? What's the one thing someone will remember?
-
-**CRITICAL**: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work - the key is intentionality, not intensity.
-
-Then implement working code (HTML/CSS/JS, React, Vue, etc.) that is:
-- Production-grade and functional
-- Visually striking and memorable
-- Cohesive with a clear aesthetic point-of-view
-- Meticulously refined in every detail
-
-## Frontend Aesthetics Guidelines
-
-Focus on:
-- **Typography**: Choose fonts that are beautiful, unique, and interesting. Avoid generic fonts like Arial and Inter; opt instead for distinctive choices that elevate the frontend's aesthetics; unexpected, characterful font choices. Pair a distinctive display font with a refined body font.
-- **Color & Theme**: Commit to a cohesive aesthetic. Use CSS variables for consistency. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.
-- **Motion**: Use animations for effects and micro-interactions. Prioritize CSS-only solutions for HTML. Use Motion library for React when available. Focus on high-impact moments: one well-orchestrated page load with staggered reveals (animation-delay) creates more delight than scattered micro-interactions. Use scroll-triggering and hover states that surprise.
-- **Spatial Composition**: Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements. Generous negative space OR controlled density.
-- **Backgrounds & Visual Details**: Create atmosphere and depth rather than defaulting to solid colors. Add contextual effects and textures that match the overall aesthetic. Apply creative forms like gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, custom cursors, and grain overlays.
-
-NEVER use generic AI-generated aesthetics like overused font families (Inter, Roboto, Arial, system fonts), cliched color schemes (particularly purple gradients on white backgrounds), predictable layouts and component patterns, and cookie-cutter design that lacks context-specific character.
-
-Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices (Space Grotesk, for example) across generations.
-
-**IMPORTANT**: Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details. Elegance comes from executing the vision well.
-
-Remember: Claude is capable of extraordinary creative work. Don't hold back, show what can truly be created when thinking outside the box and committing fully to a distinctive vision.

package/teams/teams/brain-studio/skills/code-review/SKILL.md

@@ -1,46 +0,0 @@
----
-name: 'code-review'
-description: 'Perform a standardized code review on the current changes. Use this when needing to evaluate how well the code matches our architecture docs, code quality, and so on.'
-allowed-tools:
-  - execute/runInTerminal
-  - edit/editFiles
-  - edit/createFile
-  - atlassian-rovo/*
----
-
-# Brain Studio — Code Review
-
-## Setup
-
-1. Use #tool:execute/runInTerminal to run `git diff origin/main...HEAD`. If that yields nothing, fall back to `git diff HEAD`. Use this output as the set of changes under review.
-2. Use #tool:execute/runInTerminal to run `git branch --show-current` and extract the Jira ticket key from the branch name (e.g. `BS-1056` from `BS-1056-my-feature`). If a ticket key is found, use the Atlassian Rovo MCP to fetch the issue and use its description and acceptance criteria to evaluate whether the code fulfils the ticket's intent.
-3. Inspect the diff to understand what types of changes are involved.
-4. Apply the **Doc Routing Table** in `.github/copilot-instructions.md` — use the change types you identified to determine which architecture docs to load. Use those docs as your source of truth throughout the review.
-5. If the codebase contradicts the docs, the **docs represent the target state** — flag the discrepancy rather than normalising the legacy pattern.
-
----
-
-## Review
-
-Evaluate the changes across these areas. Let the loaded architecture docs govern the specific standards — do not invent rules not found there.
-
-1. **Code Quality** — single responsibility principle, clarity, naming, redundancy, complexity, consistency with documented patterns
-2. **Regressions** — silent breakage, unexpected behaviour changes, altered logic outside of the stated scope of the ticket, downstream impact
-3. **Security** — input validation, sensitive data handling, auth correctness
-4. **Performance** — inefficient or unnecessarily expensive code, unnecessary re-renders, missing cleanups, over-importing
-5. **Error handling** — async error paths covered, error messaging in place, graceful degradation, no swallowed errors
-6. **Accessibility** — semantic HTML, ARIA attributes, keyboard navigation, focus management
-7. **Testing** — coverage of new logic, edge cases, error paths; flag superfluous tests
-8. **Documentation** — non-obvious logic commented; JSDoc updated where needed, architecture docs updated if the change introduces a new pattern or deviates from existing ones
-
----
-
-## Output Format
-
-- **Inline comments** for specific lines or blocks.
-- **Top-level observations** for broad themes or praise.
-- Prioritise by severity: 🔴 blocking / 🟡 important / 🔵 minor.
-- Do **not** include your reasoning steps or to-do list.
-- Close with a witty quatrain summarising the PR. 🎭
-
-Save the review to `docs/code-reviews/<branch-name>-code-review.md` (use the full branch name from Setup step 2). Confirm the file has been written.

package/toolsets/toolsets/rzlv-flow/README.md

@@ -1,102 +0,0 @@
-# rzlv-flow: Atlassian Intelligence Skills
-
-A toolset of modular, composable skills for Jira and Confluence developer workflows. Covers daily triage, ticket focus, wrap/sync, sprint status, context loading, and more — all without requiring the full BMAD Method or the rzlv-flow monolith.
-
-Each skill is standalone and can be installed individually or as a complete suite.
-
-## Quick Start
-
-```bash
-# 1. Install all skills + resources
-npx @groupby/ai-dev install toolset rzlv-flow
-
-# 2. Configure Atlassian MCP (see docs/mcp-setup.md)
-#    Add atlassian-rovo config to .vscode/mcp.json
-
-# 3. Use — ask your AI assistant:
-#    "Start my day"           → daily triage
-#    "Focus on PROJ-123"      → ticket deep-dive
-#    "Wrap up PROJ-123"       → wrap & sync
-```
-
-See [docs/getting-started.md](docs/getting-started.md) for a full walkthrough.
-
-## Skills
-
-| Skill | Description | Status |
-|-------|-------------|--------|
-| `jira-daily-triage` | Start-of-day ticket triage with sprint detection | Complete |
-| `jira-ticket-focus` | Deep-load a ticket with full context | Complete |
-| `jira-wrap-sync` | Wrap up work, draft comment, multi-action sync | Complete |
-| `jira-ticket-trace` | Trace code back to Jira requirements | Complete |
-| `jira-comment` | Add a comment to a Jira ticket with FCMP safety | Complete |
-| `jira-status` | Change ticket status with transition validation | Complete |
-| `jira-sprint-status` | Sprint status report with completion metrics | Complete |
-| `jira-sync` | Force-sync local Jira context with remote state | Complete |
-| `atlassian-orchestrator` | Pull surrounding ticket context and create structures | Complete |
-| `context-analyst` | Transform meeting transcripts into structured docs | Complete |
-| `confluence-publish` | Publish local markdown to Confluence with Leaf Bundle mirrors | Complete |
-| `confluence-fetch` | Pull a Confluence page into a local markdown mirror | Complete |
-
-> **Note:** `confluence-publish` provides lightweight ad-hoc publishing to Confluence. For bulk structured sync of `_docs/` folders following epic hierarchy, use `atlassian-orchestrator` Mode 3 instead.
-
-## Prerequisites
-
-### Required: Atlassian MCP (`atlassian-rovo`)
-
-All Jira and Confluence skills require the Atlassian MCP server for API access to your Atlassian instance.
-
-### Optional: GitHub MCP
-
-Only needed for PR creation features in `jira-wrap-sync`. Not required for any other skills.
-
-See [docs/mcp-setup.md](docs/mcp-setup.md) for detailed setup instructions.
-
-## Installation
-
-```bash
-npx @groupby/ai-dev install toolset rzlv-flow       # All skills + resources
-npx @groupby/ai-dev install skill jira-daily-triage   # Individual skill
-```
-
-Common options:
-
-| Flag | Description |
-|------|-------------|
-| `--target <dir>` | Install into a specific directory (defaults to cwd) |
-| `--dry-run` | Preview what would be installed without writing files |
-| `--force` | Overwrite existing files without prompting |
-| `--skip-existing` | Skip files that already exist |
-
-You can also copy skills manually from this repository into `docs/ai/skills/` and resources into `docs/ai/resources/`.
-
-## BMAD Compatibility
-
-These skills are compatible with BMAD's Jira file structure (`docs/jira/{instance}/{project}/...`) but do **not** require BMAD. They were originally developed as part of the BMAD "Atlassian Intelligence Suite" and have been extracted as standalone skills. If BMAD is installed in your project, these skills coexist without conflict.
-
-## Shared Resources
-
-Skills reference shared resource files installed to `docs/ai/resources/` in your project:
-
-| Resource | Description |
-|----------|-------------|
-| `fcmp-protocol.md` | Fetch-Compare-Merge-Push sync pattern for safe Atlassian read/write |
-| `jira-file-structure.md` | Standard directory layout for local Jira mirrors |
-| `confluence-file-structure.md` | Leaf Bundle pattern for Confluence page mirrors |
-| `sync-state-format.md` | YAML frontmatter schema for ticket and page files |
-| `confluence-page-templates/` | Starter scaffolds for Confluence pages (initiative overview, strategic context, technical architecture, decisions) |
-
-## MCP Setup Automation
-
-MCP server configuration is currently manual — see [docs/mcp-setup.md](docs/mcp-setup.md) for step-by-step instructions (~5 minutes). Automated MCP configuration via the CLI is a future enhancement.
-
-## Documentation
-
-| Doc | Description |
-|-----|-------------|
-| [docs/getting-started.md](docs/getting-started.md) | Quick walkthrough: install → configure → use |
-| [docs/mcp-setup.md](docs/mcp-setup.md) | Atlassian and GitHub MCP server configuration |
-
-## Contributing
-
-See the [architecture documentation](../../docs/architecture/README.md) for repo structure, skill authoring guides, and conventions.

package/toolsets/toolsets/rzlv-flow/docs/mcp-setup.md

@@ -1,126 +0,0 @@
-# MCP Server Setup Guide
-
-This guide covers configuring the MCP servers required by rzlv-flow skills.
-
----
-
-## Atlassian MCP (`atlassian-rovo`) — Required
-
-All Jira and Confluence skills depend on the Atlassian MCP server for API access.
-
-### VS Code Configuration
-
-Add the following to your `.vscode/mcp.json` (create the file if it doesn't exist):
-
-```json
-{
-  "servers": {
-    "atlassian-rovo": {
-      "command": "npx",
-      "args": ["-y", "@anthropic/atlassian-rovo-mcp"],
-      "env": {
-        "ATLASSIAN_SITE": "your-company.atlassian.net",
-        "ATLASSIAN_EMAIL": "you@company.com",
-        "ATLASSIAN_API_TOKEN": "${input:atlassianApiToken}"
-      }
-    }
-  },
-  "inputs": [
-    {
-      "type": "promptString",
-      "id": "atlassianApiToken",
-      "description": "Atlassian API Token",
-      "password": true
-    }
-  ]
-}
-```
-
-### Generating an API Token
-
-1. Go to [https://id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
-2. Click **Create API token**
-3. Give it a label (e.g. "VS Code MCP")
-4. Copy the generated token — you won't see it again
-
-### Verifying the Connection
-
-After configuring, ask the LLM to run a simple query:
-
-> "Search Jira for my open tickets using the Atlassian MCP"
-
-If the MCP server is configured correctly, it will call `mcp_atlassian-rovo_search` and return results. If you get an authentication error, double-check your site URL, email, and API token.
-
----
-
-## GitHub MCP — Optional
-
-Only needed for PR creation features in the `jira-wrap-sync` skill. All other skills work without it.
-
-### VS Code Configuration
-
-Add to your `.vscode/mcp.json`:
-
-```json
-{
-  "servers": {
-    "github": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:githubPat}"
-      }
-    }
-  },
-  "inputs": [
-    {
-      "type": "promptString",
-      "id": "githubPat",
-      "description": "GitHub Personal Access Token",
-      "password": true
-    }
-  ]
-}
-```
-
-### PAT Token Requirements
-
-Create a fine-grained personal access token at [https://github.com/settings/tokens?type=beta](https://github.com/settings/tokens?type=beta) with the following scopes:
-
-- **Repository access:** Select the repos you work with
-- **Permissions:**
-  - Contents: Read and write
-  - Pull requests: Read and write
-  - Metadata: Read-only
-
-### When It's Needed
-
-Only `jira-wrap-sync` uses the GitHub MCP — specifically when creating a pull request as part of the wrap-up workflow. If you don't use that feature, you can skip this setup entirely.
-
----
-
-## Troubleshooting
-
-### MCP server not starting
-
-- Ensure `npx` is available in your PATH. Run `npx --version` in your terminal.
-- Check the VS Code Output panel (View → Output → select "MCP" from the dropdown) for error messages.
-- Try running the `npx` command manually in a terminal to see if it installs and starts correctly.
-
-### Authentication failures (401)
-
-- **Atlassian:** Verify your site URL includes `.atlassian.net` (not the full `https://` URL). Confirm your email matches your Atlassian account. Regenerate the API token if needed.
-- **GitHub:** Confirm the PAT hasn't expired. Check that it has the required scopes.
-
-### Wrong Atlassian instance
-
-- `ATLASSIAN_SITE` should be just the domain, e.g. `your-company.atlassian.net` — not a full URL like `https://your-company.atlassian.net/jira`.
-
-### Rate limiting
-
-- Atlassian APIs have rate limits. If you see 429 errors, the skills will back off automatically per the FCMP protocol. Avoid running multiple sync operations in rapid succession.
-
-### MCP calls return empty results
-
-- Confirm you have permission to access the Jira project or Confluence space you're querying.
-- Check that the project key or space key is correct.

package/toolsets/toolsets/rzlv-flow/resources/README.md

@@ -1,16 +0,0 @@
-# rzlv-flow Shared Resources
-
-Resources are shared reference material installed alongside skills. They contain protocol definitions, file structure conventions, and schema specifications that multiple skills depend on.
-
-## Installation
-
-When installed via the CLI, resources are placed in `docs/ai/resources/` in the target project. Skills reference them via relative paths and may ask the LLM to load them at the start of a workflow.
-
-## Resource Files
-
-| File | Description |
-|------|-------------|
-| `fcmp-protocol.md` | Fetch-Compare-Merge-Push sync pattern — the core protocol for safe Atlassian read/write operations |
-| `jira-file-structure.md` | Standard directory layout for local Jira mirrors (`docs/jira/{instance}/{project}/...`) |
-| `confluence-file-structure.md` | Directory layout for local Confluence page mirrors with structured and flexible modes |
-| `sync-state-format.md` | YAML frontmatter schema for Jira ticket and Confluence page files |