Custom skills and agents for Claude Code - codebase research, context management, and implementation planning workflows

Claude Code skill that generates comprehensive context documents for AI agents working on your codebase

AI context toolkit for Claude Code — commands, decisions, skills, and feature planning for your codebase

Agent skill: dispatch an independent, context-free reviewer to critique implementation plans. Cross-model review (Claude/Codex), custom personas, codebase verification.

Context engineering middleware for Claude Code — intelligent codebase indexing, token-efficient file selection, local tracking, testing, auditing, and session persistence via MD files.

A Claude skill that indexes codebases with minimal context‑window overhead using tiered memory.

Portable Signature Map skill for Codex/Claude: builds a compact signatures.json (symbols, signatures, comments, lines) so agents get fast, low-cost, high-value codebase context without expensive repo-wide exploration, plus ergonomic CLI (sigmap) and one-line global/local installer.

This repository contains the codebase for an Alexa skill that integrates DeepSeek AI, bringing advanced conversational intelligence and context-aware responses to Alexa-enabled devices.

AI-powered mobile project scanner. Generates skill.md context files for legacy iOS & Android projects so Claude Code, Cursor, and Windsurf understand your codebase before touching it.

Financial app skills demonstration using Swift and SwiftUI. The Financial App codebase will be constructed with white-labelling of the app as one of the primary concerns. In the context of the FinancialApp, white-labelling is taken to mean that the app supports a default configuration

Agent skill that explores repositories by delegating to Claude Code CLI. Saves context for agents and speeds up codebase understanding.

# Unit 17 Nosql Homework: Workout Tracker For this assignment, you'll create a workout tracker. You have already been provided with the front end code in the `Develop` folder. This assignment will require you to create Mongo database with a Mongoose schema and handle routes with Express. ## User Story * As a user, I want to be able to view create and track daily workouts. I want to be able to log multiple exercises in a workout on a given day. I should also be able to track the name, type, weight, sets, reps, and duration of exercise. If the exercise is a cardio exercise, I should be able to track my distance traveled. ## Business Context A consumer will reach their fitness goals more quickly when they track their workout progress. ## Acceptance Criteria When the user loads the page, they should be given the option to create a new workout or continue with their last workout. The user should be able to: * Add exercises to a previous workout plan. * Add new exercises to a new workout plan. * View the combined weight of multiple exercises on the `stats` page. To deploy an application with a MongoDB database to Heroku, you'll need to set up a MongoDB Atlas account and connect a database from there to your application. Be sure to use the following guides for support: * [Set Up MongoDB Atlas](../04-Supplemental/MongoAtlas-Setup.md) * [Deploy with Heroku and MongoDB Atlas](../04-Supplemental/MongoAtlas-Deploy.md) ## Commit Early and Often One of the most important skills to master as a web developer is version control. Building the habit of committing via Git is important for the following two reasons: 1. Your commit history is a signal to employers that you are actively working on projects and learning new skills. 2. Your commit history allows you to revert your codebase in the event that you need to return to a previous state. Follow these guidelines for committing: * Make single-purpose commits for related changes to ensure a clean, manageable history. If you are fixing two issues, make two commits. * Write descriptive, meaningful commit messages so that you and anyone else looking at your repository can easily understand its history. * Don't commit half-done work, for the sake of your collaborators (and your future self!). * Test your application before you commit to ensure functionality at every step in the development process. We want you to have well over 200 commits by graduation, so commit early and often! ## Submission on BCS You are required to submit the following: * The URL to the deployed application * The URL to the GitHub repository

# Unit 11 Express Homework: Note Taker ## Description Create an application that can be used to write, save, and delete notes. This application will use an express backend and save and retrieve note data from a JSON file. * The application frontend has already been created, it's your job to build the backend and connect the two. * The following HTML routes should be created: * GET `/notes` - Should return the `notes.html` file. * GET `*` - Should return the `index.html` file * The application should have a `db.json` file on the backend that will be used to store and retrieve notes using the `fs` module. * The following API routes should be created: * GET `/api/notes` - Should read the `db.json` file and return all saved notes as JSON. * POST `/api/notes` - Should receive a new note to save on the request body, add it to the `db.json` file, and then return the new note to the client. * DELETE `/api/notes/:id` - Should receive a query parameter containing the id of a note to delete. This means you'll need to find a way to give each note a unique `id` when it's saved. In order to delete a note, you'll need to read all notes from the `db.json` file, remove the note with the given `id` property, and then rewrite the notes to the `db.json` file. ## User Story AS A user, I want to be able to write and save notes I WANT to be able to delete notes I've written before SO THAT I can organize my thoughts and keep track of tasks I need to complete ## Business Context For users that need to keep track of a lot of information, it's easy to forget or be unable to recall something important. Being able to take persistent notes allows users to have written information available when needed. ## Acceptance Criteria Application should allow users to create and save notes. Application should allow users to view previously saved notes. Application should allow users to delete previously saved notes. ## Deploying the App You will not be able to deploy your server side code on GitHub pages. This app should be deployed on Heroku. Carefully follow the [Heroku Guide](../04-Supplemental/HerokuGuide.md) for getting your app deployed on Heroku. - - - ## Commit Early and Often One of the most important skills to master as a web developer is version control. Building the habit of committing via Git is important for two reasons: * Your commit history is a signal to employers that you are actively working on projects and learning new skills. * Your commit history allows you to revert your codebase in the event that you need to return to a previous state. Follow these guidelines for committing: * Make single-purpose commits for related changes to ensure a clean, manageable history. If you are fixing two issues, make two commits. * Write descriptive, meaningful commit messages so that you and anyone else looking at your repository can easily understand its history. * Don't commit half-done work, for the sake of your collaborators (and your future self!). * Test your application before you commit to ensure functionality at every step in the development process. We would like you to have well over 200 commits by graduation, so commit early and often! ## Submission on BCS You are required to submit the following: * The URL of the deployed application. This should be the link to the url provided by Heroku. Be sure not to submit a link to the Heroku dashboard. * The URL of the GitHub repository - - - © 2019 Trilogy Education Services, a 2U, Inc. brand. All Rights Reserved.

Bootstraps project-specific expert skills from a codebase, with shared context and durable memory.

Build persistent AI agents that keep codebases healthy with shared skills and long-lived context

A Claude Code skill that transforms vague prompts into comprehensive, well-structured prompts with codebase context

A lightweight skill that gives AI agents durable repository context for long-running and parallel codebase development.

A set of skills that helps to onboard context for an AI picking up with a codebase

🤖 Enhance AI agents with curated skills for context engineering, enabling seamless navigation and smarter codebase interactions.

Intent-aware codebase intelligence for AI assistants. Scans codebases, builds layered semantic indexes with LLMs, and generates skill files (CLAUDE.md, .cursorrules) for instant project context.

📦 Equip agents with the Recursive Language Model skill to analyze large codebases efficiently, improving context handling and reducing errors.

A copy-and-go Sovereign SDLC starter kit for AI-assisted software development. Auto-generates project context, agent skills, and workflows from a codebase scan.

General-purpose MCP servers and Claude Code skills for AI coding agents. Context file generators, codetag surfacing, and developer workflow tools. Framework-agnostic — works with any codebase.

Clone of the Amazon Front-End and functionality to improve skills in React, React Context + have codebase form as Front-End for marketplace hosted on the Ethereum Blockchain

This repository contains a SKILL for AI coding agents (like Claude Code, Cursor, or Windsurf) based on the Context Engineering methodology. It forces the AI to work in four strict, human-verified phases (Research, Design, Planning, Implementation) to generate secure, high-quality code while preventing LLM hallucinations and codebase degradation.

# Unit 11 Express Homework: Note Taker ## Description Create an application that can be used to write, save, and delete notes. This application will use an express backend and save and retrieve note data from a JSON file. * The application frontend has already been created, it's your job to build the backend and connect the two. * The following HTML routes should be created: * GET `/notes` - Should return the `notes.html` file. * GET `*` - Should return the `index.html` file * The application should have a `db.json` file on the backend that will be used to store and retrieve notes using the `fs` module. * The following API routes should be created: * GET `/api/notes` - Should read the `db.json` file and return all saved notes as JSON. * POST `/api/notes` - Should recieve a new note to save on the request body, add it to the `db.json` file, and then return the new note to the client. * DELETE `/api/notes/:id` - Should recieve a query paramter containing the id of a note to delete. This means you'll need to find a way to give each note a unique `id` when it's saved. In order to delete a note, you'll need to read all notes from the `db.json` file, remove the note with the given `id` property, and then rewrite the notes to the `db.json` file. ## User Story AS A user, I want to be able to write and save notes I WANT to be able to delete notes I've written before SO THAT I can organize my thoughts and keep track of tasks I need to complete ## Business Context For users that need to keep track of a lot of information, it's easy to forget or be unable to recall something important. Being able to take persistent notes allows users to have written information available when needed. ## Acceptance Criteria Application should allow users to create and save notes. Application should allow users to view previously saved notes. Application should allow users to delete previously saved notes. - - - ## Commit Early and Often One of the most important skills to master as a web developer is version control. Building the habit of committing via Git is important for two reasons: * Your commit history is a signal to employers that you are actively working on projects and learning new skills. * Your commit history allows you to revert your codebase in the event that you need to return to a previous state. Follow these guidelines for committing: * Make single-purpose commits for related changes to ensure a clean, manageable history. If you are fixing two issues, make two commits. * Write descriptive, meaningful commit messages so that you and anyone else looking at your repository can easily understand its history. * Don't commit half-done work, for the sake of your collaborators (and your future self!). * Test your application before you commit to ensure functionality at every step in the development process. We would like you to have well over 200 commits by graduation, so commit early and often! ## Submission on BCS You are required to submit the following: * The URL of the deployed application * The URL of the GitHub repository - - - © 2019 Trilogy Education Services, a 2U, Inc. brand. All Rights Reserved.