slashdev 0.1.0 → 1.1.0

package/claude-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/claude-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/claude-skills/pr-description/SKILL.md

@@ -0,0 +1,35 @@
+---
+name: pr-description
+description: Generate clear, structured pull request descriptions from diffs and context
+version: "1.0"
+owner: michael@slashdev.io
+---
+
+# PR Description Generator
+
+Generate a well-structured pull request description based on the current changes.
+
+## Process
+
+1. Analyze the diff (staged and unstaged changes)
+2. Identify the type of change (feature, fix, refactor, docs, etc.)
+3. Write a concise title (under 70 characters)
+4. Write the body with:
+
+## Output Format
+
+```markdown
+## Summary
+- Bullet points describing what changed and why
+
+## Changes
+- Specific technical changes made
+
+## Testing
+- How to verify the changes work correctly
+
+## Notes
+- Any deployment considerations, migrations, or follow-up work
+```
+
+Keep descriptions factual and concise. Focus on the "why" not just the "what".

package/claude-skills/scope-estimate/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: scope-estimate
+description: Estimate scope and effort for development tasks based on codebase context
+version: "1.0"
+owner: michael@slashdev.io
+---
+
+# Scope Estimation
+
+You are a senior engineer at Slashdev estimating the scope of a development task.
+
+## Process
+
+1. Understand the requested feature or change
+2. Identify affected files, modules, and integration points
+3. Break the work into discrete subtasks
+4. Estimate effort for each subtask
+5. Flag risks and unknowns that could expand scope
+
+## Output Format
+
+### Overview
+One-paragraph summary of the work.
+
+### Subtasks
+| # | Task | Effort | Risk |
+|---|------|--------|------|
+| 1 | Description | S/M/L/XL | Low/Med/High |
+
+### Total Estimate
+- **Effort**: S (< 2hrs) / M (half day) / L (1-2 days) / XL (3+ days)
+- **Confidence**: High / Medium / Low
+
+### Risks & Unknowns
+- List anything that could change the estimate
+
+Be honest about uncertainty. A wide range with context is better than false precision.

package/claude-skills/secure-deploy/SKILL.md

@@ -0,0 +1,219 @@
+---
+name: secure-deploy
+description: Retrofit a project's CI/CD pipelines, Dockerfiles, and deploy scripts to use Socket Firewall (sfw) for all dependency installs. Use when the user asks to "secure deploy", "set up sfw in CI", "add socket firewall to production", or whenever you're editing a CI workflow / Dockerfile / deploy script that installs dependencies.
+version: "1.0"
+owner: michael@slashdev.io
+---
+
+# Secure Deploy — Retrofit projects to use Socket Firewall in production
+
+Slashdev requires every dependency install — local AND production — to be wrapped
+with Socket Firewall (`sfw`). This protects against supply-chain attacks
+(compromised packages, typosquats, dependency confusion) by scanning every package
+against Socket's vulnerability/malware database before it's allowed to install.
+
+When a developer asks you to set up production deployment, edit a CI pipeline, write
+a Dockerfile, or deploy a project, **you must ensure every install command uses `sfw`**.
+
+This skill walks you through the retrofit systematically.
+
+## When to use this skill
+
+Trigger automatically (without being asked) whenever you're about to:
+- Create or edit a `.github/workflows/*.yml` file with an `npm`/`pnpm`/`yarn`/`bun`/`composer`/`pip` install step
+- Create or edit a `Dockerfile` that runs an install command
+- Create or edit `.gitlab-ci.yml`, `bitbucket-pipelines.yml`, `circleci/config.yml`, or any other CI config
+- Create or edit a `deploy.sh`, `Procfile`, or `Makefile` install target
+- Modify the `scripts` section of `package.json` to add an install-related step
+
+Trigger explicitly when the user says: "secure deploy", "add sfw to CI", "set up socket firewall in production", "retrofit production for socket firewall", "audit deploy for sfw".
+
+## Step-by-step retrofit playbook
+
+### Step 1 — Discover deployment surface
+
+Use Glob to find every file that could install dependencies in CI or production:
+
+```
+.github/workflows/*.yml
+.github/workflows/*.yaml
+.gitlab-ci.yml
+.gitlab/*.yml
+bitbucket-pipelines.yml
+.circleci/config.yml
+azure-pipelines.yml
+Jenkinsfile
+Dockerfile
+Dockerfile.*
+*.dockerfile
+docker-compose*.yml
+Procfile
+deploy.sh
+deploy/*.sh
+scripts/deploy*.sh
+Makefile
+package.json
+```
+
+For each file found, Read it and look for any of these patterns:
+
+- `npm install`, `npm i`, `npm ci`, `npm add`
+- `pnpm install`, `pnpm i`, `pnpm add`
+- `yarn`, `yarn install`, `yarn add`
+- `bun install`, `bun i`, `bun add`
+- `composer install`, `composer require`, `composer update`
+- `pip install`, `pip3 install`, `uv install`, `uv sync`, `uv add`
+
+Note any line that already starts with `sfw ` — those are already secured and don't
+need to be touched.
+
+### Step 2 — Plan the changes
+
+For each install command found, plan one of these rewrites:
+
+**a) GitHub Actions workflow YAML**
+
+Before:
+```yaml
+- name: Install dependencies
+  run: npm ci
+```
+
+After:
+```yaml
+- name: Install Socket Firewall
+  run: npm install -g @socketsecurity/cli
+- name: Install dependencies
+  run: sfw npm ci
+```
+
+If a job has multiple install steps, only one `Install Socket Firewall` step is needed
+per job (it persists across steps because they share the same runner).
+
+**b) Dockerfile**
+
+Before:
+```dockerfile
+RUN npm ci
+```
+
+After:
+```dockerfile
+RUN npm install -g @socketsecurity/cli && sfw npm ci
+```
+
+For Composer:
+```dockerfile
+RUN npm install -g @socketsecurity/cli && sfw composer install --no-dev --optimize-autoloader
+```
+
+(npm is the simplest install vector for sfw itself; if the base image doesn't have
+Node, install Node first or use the official Socket installer.)
+
+**c) Shell deploy scripts (`deploy.sh`, etc.)**
+
+Before:
+```bash
+npm ci --omit=dev
+```
+
+After:
+```bash
+# Ensure sfw is available
+if ! command -v sfw >/dev/null 2>&1; then
+  npm install -g @socketsecurity/cli
+fi
+sfw npm ci --omit=dev
+```
+
+**d) `package.json` scripts**
+
+Before:
+```json
+{
+  "scripts": {
+    "postinstall": "npm install --prefix ./client"
+  }
+}
+```
+
+After:
+```json
+{
+  "scripts": {
+    "postinstall": "sfw npm install --prefix ./client"
+  }
+}
+```
+
+(Don't add the `npm install -g @socketsecurity/cli` step inside `package.json` — assume
+sfw is already installed wherever this script runs. If it's running in CI, the workflow
+or Dockerfile should have installed sfw at the top.)
+
+### Step 3 — Show the diff and confirm
+
+Before writing any changes, show the user a clear summary:
+
+> Found N install commands across M files. Proposed changes:
+>
+> 1. `.github/workflows/ci.yml` — wrap `npm ci` in build job (+ add sfw install step)
+> 2. `Dockerfile` — wrap `RUN npm ci` with sfw install
+> 3. `package.json` — wrap postinstall script
+>
+> Apply these changes?
+
+Use AskUserQuestion if there's any ambiguity (e.g. multiple jobs in a workflow, unclear
+whether a step is part of the build or local-only). For Dockerfiles especially, ask
+about the base image — if it doesn't have Node, the sfw install command needs to be
+different.
+
+### Step 4 — Apply the changes
+
+Use Edit to apply each change. After applying:
+
+1. **Validate YAML/JSON syntax** — for any modified `.yml` or `.json` file, run a quick
+   parse check (e.g. `python3 -c 'import yaml,sys; yaml.safe_load(open("path"))'` for
+   YAML, or `python3 -m json.tool path` for JSON). Fix any syntax errors.
+2. **Run a build smoke test if possible** — for Dockerfiles, suggest the user run
+   `docker build .` locally. For GitHub Actions, suggest pushing to a feature branch
+   and watching the workflow run.
+3. **Document what was changed** — print a final summary listing every file modified
+   and what was added.
+
+### Step 5 — Verify CI doesn't already use a different security tool
+
+If during Step 1 you find references to other security scanners (Snyk, Dependabot,
+Trivy, npm audit, etc.), don't remove them — they complement Socket Firewall, they
+don't replace it. Mention to the user: "I found existing security scanning via X. I
+left it in place — Socket Firewall complements it by blocking malicious packages
+*before* they install, while X scans the installed tree."
+
+## Important conventions
+
+- **Never silently change install commands.** Always show the diff and get
+  confirmation before writing CI/deploy files. These are production-critical files.
+- **Don't add sfw to dev-only `node_modules` install steps in `package.json`** unless
+  the user explicitly asks. The PreToolUse hook handles dev-side enforcement
+  automatically; only retrofit `package.json` scripts that run in CI/deploy contexts.
+- **Don't try to install Socket Firewall globally on the user's machine** as part of
+  this skill. That's the developer's responsibility, and the slashdev hook will warn
+  them if it's missing. This skill only modifies project files.
+- **Don't touch `.lock` files** (`package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`,
+  `composer.lock`, `bun.lockb`). They're generated.
+- **Preserve existing flags** — when wrapping `npm ci --omit=dev` with `sfw`, keep
+  the `--omit=dev` flag.
+
+## Output format
+
+Always end the skill with:
+
+```
+✓ Secured N install commands across M files:
+  - <file>: <change summary>
+  - <file>: <change summary>
+
+Next steps:
+  - Test locally (if applicable)
+  - Push to a feature branch and watch CI
+  - Confirm sfw is available in your CI environment (the install step is now in place)
+```