Packs
4 packs@samyakjhaveri
Business Process
Business process skills (process-optimizer, sop-writer, workflow-mapper, weekly-review). Useful for operational documentation, SOP generation, and workflow analysis. NOT for: software engineering tasks — these target organizational processes, not code.
4 skills · pack
@samyakjhaveri
Pocock Engineering
Engineering workflow skills from Matt Pocock's skills repo (triage, to-issues, to-prd, tdd, prototype, diagnose, grill-with-docs, improve-codebase-architecture, zoom-out). Covers issue lifecycle, TDD, prototyping, architectural review, domain grilling, and PRD generation. NOT for: daily development workflow — install individual skills as needed.
7 skills · pack
@samyakjhaveri
Sam Cc Setup
Portable core of Sam's Claude Code setup: native pre-commit hook enforcement (sentinel gate retired 2026-08-14), on-demand /validate, generic review agents, cross-model Codex review skills, and a /bootstrap-cc-setup skill that writes the always-loaded rules layer plugins cannot ship. For repos NOT bootstrapped by the Loam Copier template - a Loam-rendered project already carries most of this in .c
6 skills · pack
@testdouble
Han Plugin Builder
Guidance for building Claude Code skills, agents, and plugins. The guidance skill answers authoring questions and, run with init, vendors the full guidance set into a repo as a path-scoped rule index so the right guidance surfaces while editing skill and agent files. Opt-in and dependency-free: installed on its own, not pulled in by the han meta-plugin.
3 skills · pack
Results for “no-code”
110 skills
javiarmesto bc-al-project-context
Maintains persistent project context for Business Central AL extensions across sessions, developers, and AI agents. Combines two complementary mechanisms: Architecture Decision Records (ADRs) that capture why technical decisions were made, and Session Handoff documents that capture where the project is right now. Generates, updates, and queries both document types. Use this skill whenever starting a new coding session on an existing project, ending a session and need to document progress, onboarding a new developer or AI agent to an existing codebase, explaining why a technical decision was made, wondering why something is designed a certain way, resuming work after a break, or handing off work between team members. Also trigger when the user says 'document this decision', 'why is this designed like this', 'where did we leave off', 'catch me up', 'what was decided', 'create an ADR', 'end of session', 'handoff', or 'context for next session'.
0 · bundle
jarbitechture 48
Turn any rough prompt, half-formed idea, or task description into a finished, ready-to-send prompt optimized for Opus 4.8 (with adaptive thinking) inside the chat app — claude.ai, the Mac app, the iOS app — NOT the API. Use this skill whenever the user wants to write, rewrite, optimize, improve, sharpen, or polish a prompt for the chat app. Trigger phrases include "rewrite this prompt", "make this a better prompt", "optimize this prompt", "turn this into a prompt", "help me prompt this", "draft a prompt that...", "I want to ask...", or whenever the user pastes a draft prompt and asks for improvements. Also trigger when the user describes a task they plan to send into the chat app and clearly wants a reusable, well-structured prompt rather than a direct answer. The output is always a single, copy-pasteable prompt in a code block that the user sends as-is — never a template with placeholders. When the request concerns the user's own work, the skill retrieves the real specifics first — memory, meeting transcript
0