nemonix-cli 1.0.0

package/src/config/claude-code-config/skills/frontend-design/LICENSE.txt

@@ -0,0 +1,177 @@
+
+                                 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/src/config/claude-code-config/skills/frontend-design/SKILL.md

@@ -0,0 +1,42 @@
+---
+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/src/config/claude-code-config/skills/git-commit/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: commit
+description: Quick commit and push with minimal, clean messages
+model: haiku
+allowed-tools: Bash(git :*), Bash(npm :*), Bash(pnpm :*)
+---
+
+# Commit
+
+Quick commit with conventional message format, then push.
+
+## Context
+
+- Git state: !`git status`
+- Staged changes: !`git diff --cached --stat`
+- Unstaged changes: !`git diff --stat`
+- Recent commits: !`git log --oneline -5`
+- Current branch: !`git branch --show-current`
+
+## Workflow
+
+1. **Analyze**: Review git status
+   - Nothing staged but unstaged changes exist: `git add .`
+   - Nothing to commit: inform user and exit
+
+2. **Generate commit message**:
+   - Format: `type(scope): brief description`
+   - Types: `feat`, `fix`, `update`, `docs`, `chore`, `refactor`, `test`, `perf`, `revert`
+   - Under 72 chars, imperative mood, lowercase after colon
+   - Example: `update(statusline): refresh spend data`
+
+3. **Commit**: `git commit -m "message"`
+
+4. **Push**: `git push`
+
+## Rules
+
+- SPEED OVER PERFECTION: Generate one good message and commit
+- NO INTERACTION: Never ask questions - analyze and commit
+- AUTO-STAGE: If nothing staged, stage everything
+- AUTO-PUSH: Always push after committing
+- IMPERATIVE MOOD: "add", "update", "fix" not past tense

package/src/config/claude-code-config/skills/git-create-pr/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: create-pr
+description: Create and push PR with auto-generated title and description
+model: haiku
+allowed-tools: Bash(git :*), Bash(gh :*)
+---
+
+# Create PR
+
+Create pull request with concise, meaningful description.
+
+## Context
+
+- Current branch: !`git branch --show-current`
+- Working tree status: !`git status --short`
+- Recent commits: !`git log --oneline -5`
+- Remote tracking: !`git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "none"`
+
+## Workflow
+
+1. **Verify**: Check `git status` and current branch
+2. **Branch Safety**: **CRITICAL** - If on main/master, create descriptive branch from changes
+3. **Push**: `git push -u origin HEAD`
+4. **Analyze**: `git diff origin/main...HEAD --stat`
+5. **Generate PR**:
+   - Title: One-line summary (max 72 chars)
+   - Body: Bullet points of key changes
+6. **Submit**: `gh pr create --title "..." --body "..."`
+7. **Return**: Display PR URL
+
+## PR Format
+
+```markdown
+## Summary
+
+• [Main change or feature]
+• [Secondary changes]
+• [Any fixes included]
+
+## Type
+
+[feat/fix/refactor/docs/chore]
+```
+
+## Rules
+
+- NO verbose descriptions
+- NO "Generated with" signatures
+- Auto-detect base branch (main/master/develop)
+- Use HEREDOC for multi-line body
+- If PR exists, return existing URL
+
+User: $ARGUMENTS

package/src/config/claude-code-config/skills/git-fix-pr-comments/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: fix-pr-comments
+description: Fetch PR review comments and implement all requested changes
+allowed-tools: Bash(gh :*), Bash(git :*), Read, Edit, MultiEdit
+---
+
+# Fix PR Comments
+
+Systematically address ALL unresolved review comments until PR is approved.
+
+## Context
+
+- Current branch: !`git branch --show-current`
+- Working tree status: !`git status --short`
+- Recent commits: !`git log --oneline -3`
+
+## Workflow
+
+1. **FETCH COMMENTS**:
+   - Identify PR: `gh pr status --json number,headRefName`
+   - Get reviews: `gh pr review list --state CHANGES_REQUESTED`
+   - Get inline: `gh api repos/{owner}/{repo}/pulls/{number}/comments`
+   - Capture BOTH review comments AND inline code comments
+   - STOP if no PR found - ask user for PR number
+
+2. **ANALYZE & PLAN**:
+   - Extract exact file:line references
+   - Group by file for MultiEdit efficiency
+   - STAY IN SCOPE: NEVER fix unrelated issues
+   - Create checklist: one item per comment
+
+3. **IMPLEMENT FIXES**:
+   - BEFORE editing: ALWAYS `Read` target file first
+   - Batch changes with `MultiEdit` for same-file modifications
+   - Make EXACTLY what reviewer requested
+   - Check off each resolved comment
+
+4. **COMMIT & PUSH**:
+   - Stage: `git add -A`
+   - Commit: `fix: address PR review comments`
+   - Push: `git push`
+   - NEVER include co-author tags
+
+## Rules
+
+- Every unresolved comment MUST be addressed
+- Read files BEFORE any edits - no exceptions
+- FORBIDDEN: Style changes beyond reviewer requests
+- On failure: Return to ANALYZE phase, never skip comments
+
+User: $ARGUMENTS

package/src/config/claude-code-config/skills/git-merge/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: merge
+description: Intelligently merge branches with context-aware conflict resolution
+allowed-tools: Bash(git :*), Bash(gh :*), Read, Edit, MultiEdit, Task
+argument-hint: <branch-name>
+---
+
+# Merge
+
+Merge branches intelligently by understanding feature context and resolving conflicts efficiently.
+
+## Context
+
+- Current branch: !`git branch --show-current`
+- Working tree status: !`git status --short`
+- Target branch: $1
+- Recent commits: !`git log --oneline -5`
+
+## Workflow
+
+1. **CONTEXT GATHERING**:
+   - `git branch --show-current` to identify current branch
+   - `git status` to ensure clean working tree
+   - **CRITICAL**: Abort if uncommitted changes exist
+
+2. **FEATURE ANALYSIS**:
+   - Search PR with `gh pr list --head <branch-name>`
+   - Get PR details with `gh pr view <number> --json title,body,files`
+   - Use Task agents to gather context from PR/issue descriptions
+
+3. **MERGE ATTEMPT**:
+   - `git fetch origin <branch-name>`
+   - `git merge origin/<branch-name> --no-commit`
+   - Check status with `git status --porcelain`
+
+4. **CONFLICT DETECTION**:
+   - Clean merge: `git commit` with descriptive message
+   - Conflicts: Parse `git diff --name-only --diff-filter=U`
+
+5. **SMART RESOLUTION**: For each conflicted file:
+   - Read file to understand conflict markers
+   - Apply resolution based on context:
+     - **Feature additions**: Keep both if non-overlapping
+     - **Bug fixes**: Prefer incoming if fixing known issue
+     - **Refactors**: Analyze intent and merge carefully
+   - Use MultiEdit to resolve all conflicts
+   - **STOP**: If >10 files conflicted, ask user
+
+6. **VERIFICATION**:
+   - `git diff --cached` to review changes
+   - Check no conflict markers remain: `grep -r "<<<<<<< HEAD"`
+   - `git add -A` and commit
+
+## Conflict Resolution by Type
+
+- **package.json**: Merge dependencies, prefer higher versions
+- **Config files**: Combine settings unless mutually exclusive
+- **Source code**: Use PR/issue context to understand intent
+- **Tests**: Keep all tests unless duplicates
+- **Imports**: Merge all, deduplicate
+
+## Rules
+
+- ALWAYS gather context before merging
+- NEVER blindly accept theirs/ours without analysis
+- ABORT if conflicts exceed 10 files
+- Max 3 resolution attempts per file
+- If stuck: `git merge --abort` and report blockers

package/src/config/claude-code-config/skills/marketing-copywriting/SKILL.md

@@ -0,0 +1,72 @@
+---
+name: copywriting
+description: Marketing copywriting specialist for analyzing and improving sales copy
+allowed-tools: Read, Edit, Write, WebFetch, Grep, Glob
+argument-hint: <task-description>
+---
+
+# Copywriting
+
+Expert marketing copywriter using "The Adweek Copywriting Handbook" principles.
+
+## The 8 Pillars
+
+1. **Honesty**: Authentic personality in text
+2. **Expertise**: Deep product and market knowledge
+3. **Emotion First**: Sell with emotions, justify with logic
+4. **Simplicity**: Make everything as simple as possible
+5. **Flow**: Irresistible slide from start to finish
+6. **Proof**: Social proof and credibility elements
+7. **Urgency**: Legitimate reasons to act now
+8. **Objections**: Address concerns before they form
+
+## Analyze Copy
+
+1. **READ**: Gather content with `Read`, `WebFetch`, or `Grep`
+2. **EVALUATE**: Score against psychological buying points
+3. **DIAGNOSE**: Identify issues (flow breaks, weak headlines, missing emotion, no urgency, unclear CTA, no proof)
+4. **REPORT**: Overall score, strengths, critical issues, improvements
+
+## Improve Copy
+
+1. **UNDERSTAND CONTEXT**: Product, audience, pain point, transformation
+2. **APPLY FRAMEWORK**: Story-driven, curiosity, value stacking, objection crushing, social proof, urgency
+3. **REWRITE**: Headlines, subheadlines, opening, body, proof, value stack, urgency, CTA, P.S.
+4. **OPTIMIZE FLOW**: Vary sentence lengths, curiosity hooks, open loops, transitions
+5. **DELIVER**: Before/after comparison, 2-3 variations
+
+## Rules
+
+- EMOTION > LOGIC: Sell with feelings, justify with facts
+- SIMPLICITY FIRST: Write for the least literate
+- CREATE SLIDES: Make it impossible to stop reading
+- SPECIFIC PROOF: "97% of dentists" not "many dentists"
+- NO FALSE URGENCY: Only legitimate scarcity
+- ANTICIPATE OBJECTIONS: Answer before they think of them
+
+## Analysis Output
+
+```markdown
+# Copy Analysis: [Name]
+
+**Overall Score**: X/10
+
+## What's Working ✓
+
+- [Strengths with examples]
+
+## Critical Issues ⚠️
+
+1. **[Issue]**: [Why it's a problem]
+   - Current: "[Quote]"
+   - Impact: [Lost conversions/trust]
+
+## Improvements
+
+- **Headline**: [Suggestion]
+- **Flow**: [Where slide breaks]
+- **Emotion**: [Missing triggers]
+- **Proof**: [Needed credibility]
+```
+
+User: $ARGUMENTS