npm - @cregis-dev/cckit - Versions diffs - 0.4.1 → 0.6.1 - Mend

@cregis-dev/cckit 0.4.1 → 0.6.1

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 (795) hide show

package/templates/plugins/claude-md-management/skills/claude-md-improver/references/templates.md DELETED Viewed

@@ -1,253 +0,0 @@
-# CLAUDE.md Templates
-## Key Principles
-- **Concise**: Dense, human-readable content; one line per concept when possible
-- **Actionable**: Commands should be copy-paste ready
-- **Project-specific**: Document patterns unique to this project, not generic advice
-- **Current**: All info should reflect actual codebase state
----
-## Recommended Sections
-Use only the sections relevant to the project. Not all sections are needed.
-### Commands
-Document the essential commands for working with the project.
-```markdown
-## Commands
-| Command | Description |
-|---------|-------------|
-| `<install command>` | Install dependencies |
-| `<dev command>` | Start development server |
-| `<build command>` | Production build |
-| `<test command>` | Run tests |
-| `<lint command>` | Lint/format code |
-```
-### Architecture
-Describe the project structure so Claude understands where things live.
-```markdown
-## Architecture
-```
-<root>/
-  <dir>/    # <purpose>
-  <dir>/    # <purpose>
-  <dir>/    # <purpose>
-```
-```
-### Key Files
-List important files that Claude should know about.
-```markdown
-## Key Files
-- `<path>` - <purpose>
-- `<path>` - <purpose>
-```
-### Code Style
-Document project-specific coding conventions.
-```markdown
-## Code Style
-- <convention>
-- <convention>
-- <preference over alternative>
-```
-### Environment
-Document required environment variables and setup.
-```markdown
-## Environment
-Required:
-- `<VAR_NAME>` - <purpose>
-- `<VAR_NAME>` - <purpose>
-Setup:
-- <setup step>
-```
-### Testing
-Document testing approach and commands.
-```markdown
-## Testing
-- `<test command>` - <what it tests>
-- <testing convention or pattern>
-```
-### Gotchas
-Document non-obvious patterns, quirks, and warnings.
-```markdown
-## Gotchas
-- <non-obvious thing that causes issues>
-- <ordering dependency or prerequisite>
-- <common mistake to avoid>
-```
-### Workflow
-Document development workflow patterns.
-```markdown
-## Workflow
-- <when to do X>
-- <preferred approach for Y>
-```
----
-## Template: Project Root (Minimal)
-```markdown
-# <Project Name>
-<One-line description>
-## Commands
-| Command | Description |
-|---------|-------------|
-| `<command>` | <description> |
-## Architecture
-```
-<structure>
-```
-## Gotchas
-- <gotcha>
-```
----
-## Template: Project Root (Comprehensive)
-```markdown
-# <Project Name>
-<One-line description>
-## Commands
-| Command | Description |
-|---------|-------------|
-| `<command>` | <description> |
-## Architecture
-```
-<structure with descriptions>
-```
-## Key Files
-- `<path>` - <purpose>
-## Code Style
-- <convention>
-## Environment
-- `<VAR>` - <purpose>
-## Testing
-- `<command>` - <scope>
-## Gotchas
-- <gotcha>
-```
----
-## Template: Package/Module
-For packages within a monorepo or distinct modules.
-```markdown
-# <Package Name>
-<Purpose of this package>
-## Usage
-```
-<import/usage example>
-```
-## Key Exports
-- `<export>` - <purpose>
-## Dependencies
-- `<dependency>` - <why needed>
-## Notes
-- <important note>
-```
----
-## Template: Monorepo Root
-```markdown
-# <Monorepo Name>
-<Description>
-## Packages
-| Package | Description | Path |
-|---------|-------------|------|
-| `<name>` | <purpose> | `<path>` |
-## Commands
-| Command | Description |
-|---------|-------------|
-| `<command>` | <description> |
-## Cross-Package Patterns
-- <shared pattern>
-- <generation/sync pattern>
-```
----
-## Update Principles
-When updating any CLAUDE.md:
-1. **Be specific**: Use actual file paths, real commands from this project
-2. **Be current**: Verify info against the actual codebase
-3. **Be brief**: One line per concept when possible
-4. **Be useful**: Would this help a new Claude session understand the project?

package/templates/plugins/claude-md-management/skills/claude-md-improver/references/update-guidelines.md DELETED Viewed

@@ -1,150 +0,0 @@
-# CLAUDE.md Update Guidelines
-## Core Principle
-Only add information that will genuinely help future Claude sessions. The context window is precious - every line must earn its place.
-## What TO Add
-### 1. Commands/Workflows Discovered
-```markdown
-## Build
-`npm run build:prod` - Full production build with optimization
-`npm run build:dev` - Fast dev build (no minification)
-```
-Why: Saves future sessions from discovering these again.
-### 2. Gotchas and Non-Obvious Patterns
-```markdown
-## Gotchas
-- Tests must run sequentially (`--runInBand`) due to shared DB state
-- `yarn.lock` is authoritative; delete `node_modules` if deps mismatch
-```
-Why: Prevents repeating debugging sessions.
-### 3. Package Relationships
-```markdown
-## Dependencies
-The `auth` module depends on `crypto` being initialized first.
-Import order matters in `src/bootstrap.ts`.
-```
-Why: Architecture knowledge that isn't obvious from code.
-### 4. Testing Approaches That Worked
-```markdown
-## Testing
-For API endpoints: Use `supertest` with the test helper in `tests/setup.ts`
-Mocking: Factory functions in `tests/factories/` (not inline mocks)
-```
-Why: Establishes patterns that work.
-### 5. Configuration Quirks
-```markdown
-## Config
-- `NEXT_PUBLIC_*` vars must be set at build time, not runtime
-- Redis connection requires `?family=0` suffix for IPv6
-```
-Why: Environment-specific knowledge.
-## What NOT to Add
-### 1. Obvious Code Info
-Bad:
-```markdown
-The `UserService` class handles user operations.
-```
-The class name already tells us this.
-### 2. Generic Best Practices
-Bad:
-```markdown
-Always write tests for new features.
-Use meaningful variable names.
-```
-This is universal advice, not project-specific.
-### 3. One-Off Fixes
-Bad:
-```markdown
-We fixed a bug in commit abc123 where the login button didn't work.
-```
-Won't recur; clutters the file.
-### 4. Verbose Explanations
-Bad:
-```markdown
-The authentication system uses JWT tokens. JWT (JSON Web Tokens) are
-an open standard (RFC 7519) that defines a compact and self-contained
-way for securely transmitting information between parties as a JSON
-object. In our implementation, we use the HS256 algorithm which...
-```
-Good:
-```markdown
-Auth: JWT with HS256, tokens in `Authorization: Bearer <token>` header.
-```
-## Diff Format for Updates
-For each suggested change:
-### 1. Identify the File
-```
-File: ./CLAUDE.md
-Section: Commands (new section after ## Architecture)
-```
-### 2. Show the Change
-```diff
- ## Architecture
- ...
-+## Commands
-+
-+| Command | Purpose |
-+|---------|---------|
-+| `npm run dev` | Dev server with HMR |
-+| `npm run build` | Production build |
-+| `npm test` | Run test suite |
-```
-### 3. Explain Why
-> **Why this helps:** The build commands weren't documented, causing
-> confusion about how to run the project. This saves future sessions
-> from needing to inspect `package.json`.
-## Validation Checklist
-Before finalizing an update, verify:
-- [ ] Each addition is project-specific
-- [ ] No generic advice or obvious info
-- [ ] Commands are tested and work
-- [ ] File paths are accurate
-- [ ] Would a new Claude session find this helpful?
-- [ ] Is this the most concise way to express the info?

package/templates/plugins/code-simplifier/.claude-plugin/plugin.json DELETED Viewed

@@ -1,9 +0,0 @@
-{
-  "name": "code-simplifier",
-  "version": "1.0.0",
-  "description": "Agent that simplifies and refines code for clarity, consistency, and maintainability while preserving functionality",
-  "author": {
-    "name": "Anthropic",
-    "email": "support@anthropic.com"
-  }
-}

package/templates/plugins/code-simplifier/LICENSE DELETED Viewed

@@ -1,202 +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
-   APPENDIX: How to apply the Apache License to your work.
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-   Copyright [yyyy] [name of copyright owner]
-   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/templates/plugins/code-simplifier/agents/code-simplifier.md DELETED Viewed

@@ -1,52 +0,0 @@
----
-name: code-simplifier
-description: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
-model: opus
----
-You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions. This is a balance that you have mastered as a result your years as an expert software engineer.
-You will analyze recently modified code and apply refinements that:
-1. **Preserve Functionality**: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.
-2. **Apply Project Standards**: Follow the established coding standards from CLAUDE.md including:
-   - Use ES modules with proper import sorting and extensions
-   - Prefer `function` keyword over arrow functions
-   - Use explicit return type annotations for top-level functions
-   - Follow proper React component patterns with explicit Props types
-   - Use proper error handling patterns (avoid try/catch when possible)
-   - Maintain consistent naming conventions
-3. **Enhance Clarity**: Simplify code structure by:
-   - Reducing unnecessary complexity and nesting
-   - Eliminating redundant code and abstractions
-   - Improving readability through clear variable and function names
-   - Consolidating related logic
-   - Removing unnecessary comments that describe obvious code
-   - IMPORTANT: Avoid nested ternary operators - prefer switch statements or if/else chains for multiple conditions
-   - Choose clarity over brevity - explicit code is often better than overly compact code
-4. **Maintain Balance**: Avoid over-simplification that could:
-   - Reduce code clarity or maintainability
-   - Create overly clever solutions that are hard to understand
-   - Combine too many concerns into single functions or components
-   - Remove helpful abstractions that improve code organization
-   - Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
-   - Make the code harder to debug or extend
-5. **Focus Scope**: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.
-Your refinement process:
-1. Identify the recently modified code sections
-2. Analyze for opportunities to improve elegance and consistency
-3. Apply project-specific best practices and coding standards
-4. Ensure all functionality remains unchanged
-5. Verify the refined code is simpler and more maintainable
-6. Document only significant changes that affect understanding
-You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.

package/templates/plugins/commit-commands/.claude-plugin/plugin.json DELETED Viewed

@@ -1,9 +0,0 @@
-{
-  "name": "commit-commands",
-  "description": "Streamline your git workflow with simple commands for committing, pushing, and creating pull requests",
-  "author": {
-    "name": "Anthropic",
-    "email": "support@anthropic.com"
-  }
-}