This repository serves as the primary source for .NET documentation (learn.microsoft.com/dotnet). It contains conceptual guides, API references, and runnable code samples demonstrating .NET language features, frameworks, and best practices. The repository is not a single application but a curated collection of educational materials organized by technology domain (e.g., C#, ASP.NET Core, Orleans, AI). Code samples illustrate patterns like dependency injection, logging, serialization, and data access, often with minimal, self-contained examples. Maintenance is active via GitHub Actions workflows for linting, dependency updates, and version sweeping, ensuring content stays current with .NET releases.
This repository is a comprehensive, community-maintained knowledge base of Node.js best practices — not a runnable application or data pipeline. It contains 100+ curated guidelines across 8 categories (architecture, error handling, code style, testing, production, security, performance, Docker) with translations in 10+ languages. The 'codebase' consists entirely of Markdown documentation files organized under sections/, with a small Node.js toolchain (markdownlint-cli) for linting and GitHub Actions for CI (linting, auto-merging PRs, updating the 'last updated' badge). There are no runtime entry points, APIs, or data flows. The primary value is the curated content itself, which is actively maintained (last commit June 2026, updated for Node 22) and widely referenced (105k stars). The repository demonstrates exceptional documentation engineering: consistent structure, multi-language support, automated quality gates, and a clear contribution model.
The Data Engineering Wiki is a community-maintained knowledge base dedicated to documenting data engineering concepts, tools, and best practices. Rather than being an executable application or data processing pipeline, it serves as a comprehensive reference resource for individuals learning and working in the data engineering field. The repository is organized into thematic sections covering foundational concepts (data architecture, modeling, processing, storage), practical tools and technologies, implementation guides, frequently asked questions, and curated learning resources. Structurally, the wiki follows a logical progression from theoretical foundations to practical application, with concepts explained through clear definitions, diagrams, and real-world examples. Key strengths include its comprehensive coverage of both established and emerging data engineering topics, practical guides on data pipeline best practices and testing methodologies, and active maintenance evidenced by recent commits. The content is presented in an accessible markdown format with consistent frontmatter, making it easy to navigate and consume. While not containing executable code or data pipelines itself, the wiki provides reusable knowledge assets in the form of methodological guides and reference materials that can be directly applied to data engineering projects. Notably, the Data Pipeline Best Practices and Testing Your Data Pipeline guides offer actionable frameworks for building reliable, scalable data systems. The repository's value lies in its role as a living document that captures and organizes community knowledge to support learning and professional practice in data engineering.
GPTLint is a linting tool that uses Large Language Models (LLMs) to enforce code quality rules. It employs a two-pass approach: a faster, cheaper LLM model identifies potential violations, and a more accurate, expensive model validates them to reduce false positives. The tool supports both built-in and custom rules defined in markdown files, caches results to avoid reprocessing unchanged files, and provides both a CLI and programmatic API. The architecture is modular, with separate components for configuration, rule parsing, linting, caching, and LLM abstraction.
This is the official OWASP Cheat Sheet Series repository, providing concise, actionable security guidance for developers. It contains over 150 markdown cheat sheets covering web application security, cloud security, AI security, and more. The repository is primarily a documentation project but includes a sophisticated build system (MkDocs, Docker, CI/CD) and tooling for quality assurance: markdown linting, link checking, text linting, and automated PR review agents. The link checker is a standout reusable component with modular architecture. The project is actively maintained with strict quality gates and a well-defined contribution process.
The OWASP Web Security Testing Guide (WSTG) is a comprehensive, community-maintained documentation project defining standard test cases for web application security assessments. It is primarily a structured knowledge base written in Markdown, organized by testing categories including Information Gathering, Authentication, Injection, and API Testing. The repository also serves as the source for multiple derived artifacts: a Jekyll static website (wstg.owasp.org), downloadable PDF/EPUB ebooks via a Pandoc+Typst pipeline, and machine-readable test checklists in JSON, XLSX, and Markdown formats. The build infrastructure includes Python scripts for site generation and navigation, GitHub Actions for CI/CD (linting, link checking, deployment), and a versioned release process that supports multiple channels (latest, stable, past versions). Although the primary content is documentation, the repository functions as a publication platform with significant automation and is actively maintained by a community of contributors. It is not a software application in the traditional sense, but the build tooling and CI/CD pipelines qualify it as an application-focused project with strong data engineering characteristics in its checklist generation and structured content management.
ghqr is a Go-based CLI tool for scanning GitHub enterprises, organizations, and repositories against a comprehensive set of best-practice rules. It produces actionable reports in Markdown, Excel, and JSON formats, with prioritized findings, remediation plans, and manual checklists. The tool also includes an MCP (Model Context Protocol) server for AI assistant integration, enabling interactive scanning and recommendations via stdio or HTTP/SSE. A deterministic mock generator allows demos and testing without live API calls. The architecture follows a composable pipeline pattern: initialization, data loading (from live API or JSON replay), enterprise/GHES/organization/repository discovery and scanning, evaluation against YAML-defined rules, and report rendering. Scanners use both REST and GraphQL APIs with batch queries, rate-limit handling, and tri-state boolean support for GHES on-prem instances. The rule registry is embedded as YAML files, loaded at startup into a typed registry that evaluators reference by stable rule IDs. Key entry points are the `ghqr scan`, `ghqr mcp`, `ghqr mock`, and `ghqr list-recommendations` commands. External dependencies include the GitHub API (REST and GraphQL), the `excelize` library for Excel output, and the `mcp-go` library for MCP protocol support. The tool is containerized via Docker and published to GHCR, with install scripts for Linux, macOS, and Windows.
This repository is the source for the C++ Core Guidelines, an evolving set of rules for writing modern C++ safely and effectively. The primary artifact is a large Markdown document (CppCoreGuidelines.md) that is rendered to HTML via Jekyll and published to isocpp.github.io. The repo also contains supporting tooling: a Python style checker that lints C++ code snippets embedded in the Markdown, a script that splits Markdown into prose and code blocks for validation, a Hunspell dictionary for spell-checking the document, and Node.js-based remark configuration for Markdown linting. CI is provided through GitHub Actions, with a legacy Travis configuration still present.
The thoughtbot/guides repository is a collection of best practice guides for software development covering a wide range of topics including programming languages, frameworks, tools, and processes. Each guide is written in Markdown and provides concrete recommendations for writing clean, maintainable code and following effective workflows. The repository serves as an internal reference for thoughtbot developers and is publicly available for others to benefit from. The architecture of the repository is straightforward: it consists of a hierarchical directory structure where each topic has its own directory containing a README.md and potentially additional files (such as sample code, how-to guides, and subdirectories). The repository includes a template directory (_template) that provides a standardized structure for creating new guides, ensuring consistency across the documentation. Maintenance is supported by automated linting via GitHub Actions and Lefthook, which enforce Markdown style guidelines. While the repository does not contain executable code, it exemplifies good documentation practices and provides a reusable template for creating similar guide collections. The highlighted component is the guide template, which demonstrates a pattern for structuring documentation that can be extracted and adapted for other projects. The repository is actively maintained, as evidenced by recent commits and ongoing issue triage, and shows low technical drift with up-to-date dependencies and configurations.
This repository is a comprehensive knowledge base and reference implementation for Claude Code best practices, curated by Shayan Rais. It is not a standalone application but rather a living documentation and configuration library that demonstrates how to effectively use Claude Code CLI through agents, skills, commands, hooks, and workflows. The core architecture follows a Command → Agent → Skill orchestration pattern, with working examples such as a weather reporter system and a structured RPI (Research-Plan-Implement) development workflow. The repository includes reusable configuration patterns (YAML frontmatter schemas for agents and skills), a cross-platform Python hook script for lifecycle events, detailed changelogs that track drift against official Claude Code documentation, and extensive reference guides covering settings, environment variables, MCP servers, and startup flags. While primarily a documentation and reference project, it contains runnable Claude Code configurations that can be directly adopted or adapted by other projects.
Kaspresso is a comprehensive Android UI testing framework built on top of Espresso (via Kakao) and UI Automator (via Kautomator), providing a Kotlin DSL for writing stable, readable tests. It offers extensive built-in reliability mechanisms: flaky safety (automatic retries with configurable timeouts), auto-scroll fallback, system dialog handling, and element reloading. The framework includes a modular interceptor architecture for customizing test behavior, device manipulation APIs (network, location, phone, permissions, logcat, screenshots, video recording), and integration with Allure for reporting and Jetpack Compose for modern UI testing. Additionally, it provides an ADB server for executing shell commands on the device and a command-line tool for generating page objects from UI dumps. The codebase is well-structured with multi-module Gradle projects, convention plugins, and extensive sample apps demonstrating real-world usage.
HTML5 Boilerplate is a professional front-end template for building fast, robust, and adaptable web apps or sites. It provides a minimal, well-structured starting point with sensible defaults, including HTML5 semantics, CSS normalization (via main.css), responsive viewport meta tag, Open Graph placeholders, favicon and touch icon setup, and a simple web app manifest. The repository also includes a build system based on Gulp for packaging the distribution archive, and Webpack configurations for development server and production bundling. The codebase is lean and focused: the actual 'dist' output is a static site skeleton, while the build tooling and tests are the primary active components. The project is well-maintained, follows modern JavaScript standards (ES modules, ESLint flat config), and is easily customizable for any static site or simple web application.
This is the official repository for The Modern JavaScript Tutorial (javascript.info). It is primarily an educational resource containing structured articles, code examples, and interactive exercises covering JavaScript fundamentals, browser APIs, network, animations, and more. The codebase is not a software application but a collection of teaching materials. The code examples are well-crafted, demonstrate modern practices, and include patterns like throttling, debouncing, promise-based helpers, custom elements, and event delegation. While the examples are tightly coupled to the tutorial context, several utility functions (e.g., cookie helpers, animation timing functions) are self-contained and could be extracted for reuse. The repository follows a logical chapter hierarchy and includes solution views with test files. It is actively maintained with recent updates reflecting current JavaScript standards.
This repository is a documentation-focused resource providing security guidelines for SaaS startups organized by company growth phases. It contains no executable code or data processing pipelines, but rather offers educational content in Markdown format covering topics from basic security hygiene (password management, encryption) to advanced compliance and incident response strategies. The material is structured as a practical guide referencing real-world scenarios and external resources, with accompanying images illustrating key concepts. While not a software project, it functions as a reusable knowledge base that engineers can reference when implementing security practices in early-stage startups.
This repository is an opinionated Angular style guide by John Papa, primarily targeting AngularJS (1.x). It is not a runnable application but a comprehensive documentation resource prescribing coding conventions, architecture patterns (LIFT, modularity, folder-by-feature), and best practices for building Angular 1 applications. The repo contains the full guide in English and 12+ community-translated versions, along with editor snippets for various IDEs. While no executable code exists, the guide itself serves as a reference for legacy Angular projects and continues to receive maintenance (last commit 2026-04-30). The companion guide for Angular 2+ is largely a stub pointing to official documentation.
This repository is a production-grade Next.js application (v14 with App Router) that serves as the official web eco-design best practices reference (Référentiel d'écoconception web) by GreenIT.fr. It provides a multi-language (French, English, Spanish) content site with a headless CMS (TinaCMS) for editing, a REST API for programmatic access, and a client-side search (Pagefind). The core content is a structured collection of 115+ best practice sheets (fiches) with frontmatter metadata including lifecycle stages, environmental impact, validation rules, and version tracking. The site is deployed on Vercel and uses MongoDB for TinaCMS indexing. While the primary purpose is an application, the underlying content is a well-structured, versioned dataset that could be used independently for compliance checking or analytical purposes, giving the repo a hybrid character. The application code is well-organized with reusable patterns for MDX rendering, glossary tooltips, content validation, and multi-referential configuration.
This repository is a curated knowledge base for professional software engineers, not a functional application or data pipeline. It consists of a large README with categorized links to articles, books, talks, and other resources, along with supplementary directories for antipatterns (with small Python code examples), training curricula for front-end and web development, and a glossary. The codebase is purely documentation and illustrative snippets; there are no services, APIs, or executable systems. Its value lies in the curated collection of high-quality references rather than in any software component. The antipatterns section provides well-written explanations of common mistakes, and the training outlines offer structured learning paths. However, there are no reusable software components—the Python files are trivial examples tied to the documentation.
Despite being classified as application-oriented, henki_ros2_best_practices contains no executable software. It is a documentation/standards repository: a single, carefully authored Markdown document (henki_ros2_best_practices.md) codifying architecture and clean-code guidelines for ROS 2 development, plus a README explaining how to integrate the document into AI coding workflows (e.g., Claude Code via CLAUDE.md) and a pointer to a companion examples repo comparing agent-generated ROS 2 packages with and without the practices applied. The actual deliverable is a concise, opinionated standards document covering node single-responsibility, separation of application logic from ROS 2 communication, launch file conventions (XML preferred), YAML config-based parameter handling, throttled logging, semantic custom message interfaces in '_msgs' packages, service-vs-action selection with enum-style error codes, C++ for performance-critical loops, SingleThreadedExecutor preference, rosdep/vcs-tool dependency management, package documentation requirements, and unit-test-first strategies that avoid flaky ROS communication sleeps. In production, this repository functions as a knowledge artifact rather than a running system: humans read it as a reference, and AI coding agents consume it as an enforced standard when generating ROS 2 packages. There are no API endpoints, data flows, or runtime dependencies; its 'architecture' is the structure and specificity of the guidelines themselves. The document is self-contained and could be dropped into any ROS 2 team's repository or agent configuration with minimal adaptation, making it a genuinely reusable engineering asset despite the complete absence of code.
PHP The Right Way is a static documentation website built with Jekyll, providing authoritative best-practice guidance for PHP developers. The repository contains markdown content files organized into chapters and sub-chapters, a set of Jekyll layouts and includes for rendering, and CSS/LESS stylesheets for presentation. It is not a software application or data pipeline—it is a content-driven site that is compiled into static HTML and hosted on GitHub Pages. The architecture is straightforward: Jekyll processes markdown posts through Liquid templates to produce a multi-page reference guide. There are no runtime PHP scripts, APIs, or executable components; all PHP code examples within the markdown are illustrative snippets for pedagogical purposes.
这是一个 Python 项目工程化开发指南的文档仓库，使用 MkDocs 构建为静态网站。仓库本身不提供可直接运行的应用程序或 API，而是面向 Python 初学者和中级开发者，提供从环境搭建、项目结构、编码规范到测试、打包发布的完整工程化实践指南。内容涵盖应用开发（包含 ETL 示例）和数据开发（基于 PySpark 的 ETL 教程），但整体以文档形式存在。代码库中唯一的可执行配置是 GitHub Actions 工作流，用于检测 Markdown 格式并部署文档页面。