Skip to content

aiskillstore/marketplace / skills/abdul-haseeb360/crud-with-spec-kit

crud-with-spec-kit

Verified

A conceptual skill for implementing CRUD features driven by Spec-Kit and Claude Code

FileKindSize
SKILL.mdskill md7.3 KB
skill-report.jsonconfig9.3 KB

skill-report.json

View on GitHub
{
  "schema_version": "2.0",
  "meta": {
    "generated_at": "2026-07-18T09:33:47.764Z",
    "slug": "abdul-haseeb360-crud-with-spec-kit",
    "source_url": "https://github.com/Abdul-Haseeb360/Hackathon-II-AI-Native-Systems/tree/main/.claude/skills/crud-with-spec-kit",
    "source_ref": "main",
    "model": "claude",
    "analysis_version": "3.0.0",
    "source_type": "community",
    "content_hash": "07f12106c12a903bea6b5dee5d5e505cb3dce01e3c2d180d918e36a23107a211",
    "tree_hash": "4df4771bcb23949fafa81d9013622403621031de113367353003755f0097ceab",
    "provenance": {
      "model_effective": "claude",
      "fallback_chain": [
        {
          "agent": "codex",
          "outcome": "failed",
          "error": "2026-07-18T09:33:47.898596Z ERROR codex_models_manager::manager: failed to refresh available models: Missing environment variable: `HELM_API_KEY`.\n2026-07-18T09:33:47.920126Z ERROR codex_models_manage…"
        },
        {
          "agent": "claude",
          "outcome": "success"
        }
      ],
      "analysis_version": "3.0.0"
    }
  },
  "skill": {
    "name": "CRUD with Spec-Kit",
    "description": "Guide Claude Code through specification-driven CRUD planning, scaffolding, validation, and testing for data-driven applications.",
    "summary": "Turn clear Spec-Kit requirements into a structured CRUD implementation plan.",
    "icon": "📦",
    "version": "1.0.0",
    "author": "Claude",
    "license": "MIT",
    "category": "coding",
    "tags": [
      "crud",
      "spec-kit",
      "api-design",
      "code-scaffolding",
      "testing"
    ],
    "supported_tools": [
      "claude",
      "codex",
      "claude-code"
    ],
    "risk_factors": []
  },
  "security_audit": {
    "risk_level": "safe",
    "is_blocked": false,
    "safe_to_publish": true,
    "analysis_status": "ok",
    "summary": "The reviewed skill is documentation-only and contains no executable code, network instructions, or credential handling. No static or semantic security findings were identified in SKILL.md.",
    "remediation": [],
    "risk_factor_evidence": [],
    "static_findings": [],
    "finding_verdicts": [],
    "semantic_findings": [],
    "critical_findings": [],
    "high_findings": [],
    "medium_findings": [],
    "low_findings": [],
    "dangerous_patterns": [],
    "files_scanned": 1,
    "total_lines": 192,
    "audit_model": "claude",
    "audited_at": "2026-07-18T09:33:47.764Z",
    "agent_auto_install_policy": "allowed",
    "manual_install_policy": "allowed"
  },
  "content": {
    "user_title": "Build CRUD Features from Clear Specifications",
    "value_statement": "CRUD work often becomes inconsistent when requirements, APIs, and user interfaces drift apart. This skill provides a structured process to translate Spec-Kit requirements into implementation, validation, and testing tasks.",
    "seo_keywords": [
      "Claude",
      "Codex",
      "Claude Code",
      "CRUD development",
      "Spec-Kit",
      "REST API design",
      "API scaffolding",
      "frontend client generation",
      "specification-driven development",
      "CRUD testing"
    ],
    "actual_capabilities": [
      "Extract entities, attributes, relationships, constraints, and required operations from a Spec-Kit specification.",
      "Plan RESTful create, read, update, and delete endpoints with suitable HTTP methods and responses.",
      "Outline frontend API clients, data models, service layers, forms, and list views for CRUD workflows.",
      "Map validation rules, error handling, and response formats to stated specification requirements.",
      "Create a traceability checklist that compares implemented features with success criteria.",
      "Suggest unit, integration, and validation tests for CRUD operations."
    ],
    "limitations": [
      "It provides conceptual guidance and does not include executable generators or framework-specific source code.",
      "It requires complete, stable specifications with clear entities, relationships, and success criteria.",
      "It is not designed for complex domain workflows that extend substantially beyond standard CRUD operations.",
      "Generated plans and code suggestions require human review for security, performance, and product requirements."
    ],
    "use_cases": [
      {
        "title": "Plan a new resource API",
        "description": "Turn a defined entity and its rules into a route, validation, response, and test plan.",
        "target_user": "Backend developer"
      },
      {
        "title": "Align a frontend with an API",
        "description": "Map CRUD endpoints to client services, data models, forms, lists, and error states.",
        "target_user": "Frontend developer"
      },
      {
        "title": "Review specification coverage",
        "description": "Compare required entities, operations, validations, and success criteria against an implementation plan.",
        "target_user": "Technical lead"
      }
    ],
    "prompt_templates": [
      {
        "title": "Identify CRUD requirements",
        "scenario": "Beginner: start from a small entity specification.",
        "prompt": "Read this Spec-Kit entity specification. List its fields, validation rules, and required create, read, update, and delete operations: [paste specification]."
      },
      {
        "title": "Design REST endpoints",
        "scenario": "Intermediate: define a backend API contract.",
        "prompt": "Using this specification, propose REST endpoints for each CRUD operation. Include HTTP methods, request fields, response fields, status codes, and validation errors: [paste specification]."
      },
      {
        "title": "Plan frontend CRUD screens",
        "scenario": "Advanced: connect user interfaces to an existing API.",
        "prompt": "Based on this entity specification and API contract, plan the frontend data model, service methods, list view, detail view, create form, edit form, deletion flow, and error states: [paste materials]."
      },
      {
        "title": "Audit implementation coverage",
        "scenario": "Advanced: verify work against acceptance criteria.",
        "prompt": "Compare the following specification with this implementation summary. Produce a traceability table of requirement, implementation status, evidence, gaps, and recommended tests: [paste specification and summary]."
      }
    ],
    "output_examples": [
      {
        "input": "A Task entity has title, due date, status, and an owner. Users can create, list, view, update, and delete tasks.",
        "output": [
          "Entities: Task and Owner relationship.",
          "Endpoints: create, list, retrieve, update, and delete Task resources.",
          "Validation: require title and owner; restrict status to approved values.",
          "Tests: cover valid requests, missing fields, invalid status, missing tasks, and authorization rules."
        ]
      },
      {
        "input": "Review whether a project implementation satisfies the specification for customer records.",
        "output": [
          "Implemented: customer list and detail retrieval.",
          "Gap: update validation does not enforce the required email format.",
          "Gap: deletion behavior is not documented.",
          "Recommended next step: add validation tests and define deletion response behavior."
        ]
      }
    ],
    "best_practices": [
      "Provide stable specifications that define entities, constraints, relationships, and acceptance criteria before requesting implementation work.",
      "Review generated API and interface plans with domain experts before creating production code.",
      "Test validation, authorization, error responses, and edge cases for every CRUD operation."
    ],
    "anti_patterns": [
      "Do not use incomplete specifications as the only source of business rules.",
      "Do not treat generated scaffolding as production-ready without security and performance review.",
      "Do not force complex workflow or policy logic into generic CRUD endpoints."
    ],
    "faq": [
      {
        "question": "What is Spec-Kit?",
        "answer": "In this skill, Spec-Kit refers to structured feature specifications that define entities, requirements, constraints, and success criteria."
      },
      {
        "question": "Does this skill generate executable code?",
        "answer": "No. It is a conceptual guide that helps an AI assistant plan and structure CRUD implementation work."
      },
      {
        "question": "Which applications fit this skill?",
        "answer": "It fits data-driven applications with clear entities, standard CRUD operations, and stable requirements."
      },
      {
        "question": "Can I use it with Claude Code?",
        "answer": "Yes. The skill is written for Claude Code workflows and can also inform compatible AI coding assistants."
      },
      {
        "question": "Does it replace security review?",
        "answer": "No. You must review authentication, authorization, input validation, data exposure, and deployment configuration separately."
      },
      {
        "question": "How should I start?",
        "answer": "Provide a concise specification with entity fields, relationships, required operations, validation rules, and acceptance criteria."
      }
    ]
  },
  "file_structure": [
    {
      "name": "SKILL.md",
      "type": "file",
      "path": "SKILL.md",
      "lines": 192
    }
  ]
}
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall