The Front-End Checklist is a comprehensive, open-source platform for front-end quality assurance, targeting both human developers and AI agents. It delivers a curated corpus of 386+ best-practice rules across 11 categories (HTML, CSS, JavaScript, Performance, Accessibility, SEO, Security, Images, Testing, Privacy, i18n) via a Next.js web application, a Model Context Protocol (MCP) server, and a standalone CLI. The architecture is a pnpm monorepo with shared packages for authentication (Better Auth + Prisma), design system (Radix UI), analytics (OpenPanel), state management (Zustand), search (FlexSearch), storage (IndexedDB), and validation. The MCP server exposes 11 tools (audit_url, review_code, search_rules, etc.) for AI-assisted code review and URL auditing, while the CLI provides offline audit capabilities. The web app offers rule browsing, user checklists with progress tracking, guides, and public profiles. The system is production-deployed on Vercel with PostgreSQL, Sentry error tracking, and Upstash rate limiting.
This is a Laravel package that provides a simple, flexible way to define and render breadcrumbs in Laravel applications. It allows developers to define breadcrumb trails using closures in a dedicated file (routes/breadcrumbs.php by default), supporting parent-child relationships, route-bound breadcrumbs, custom data, before/after callbacks, and macros. The package generates a collection of breadcrumb objects and renders them using Blade views, with built-in templates for Bootstrap 4/5, Bulma, Foundation 6, JSON-LD structured data, Materialize, Tailwind CSS, and UIkit. The architecture consists of a Manager singleton that orchestrates registration and rendering, a Generator class that recursively builds the breadcrumb trail by calling user-defined closures, and a Facade for convenient access. The codebase is well-structured, thoroughly tested (30+ test files), and includes helpful exception handling with Laravel Ignition solutions. It is actively maintained and supports Laravel 10 through 13 with PHP 8.1+.
This repository is a Next.js SEO library that provides React components for generating JSON-LD structured data (Schema.org) to enhance search engine optimization. The library offers over 50 specialized components for various Schema.org types (Article, Recipe, Product, Event, etc.) and a core JsonLdScript component for rendering JSON-LD tags. It includes utility processors for normalizing flexible input data into Schema.org-compliant formats and emphasizes security through XSS prevention in JSON-LD stringification. The architecture follows a modular component pattern with strong TypeScript typing, comprehensive testing (unit and E2E), and support for both Pages Router and App Router in Next.js. The library is actively maintained with recent updates, a changeset-based versioning system, and extensive documentation.
OPC Skills is a curated marketplace and toolchain of AI agent skills designed for solopreneurs, indie hackers, and one-person companies. The repository contains 9 skills (reddit, twitter, producthunt, domain-hunter, logo-creator, banner-creator, nanobanana, seo-geo, requesthunt, archive) that each provide structured prompts and Python scripts to automate tasks like market research, SEO/GEO optimization, domain hunting, logo/banner creation, and social media analysis. Skills are distributed via the Agent Skills standard (`npx skills add`) and also available as a Claude Code plugin. The project includes a full website at opc.dev powered by a Cloudflare Worker (website/worker.js) with per-skill pages, a blog, SEO/GEO optimization, and install statistics tracking. CI/CD pipelines deploy the website, test installs across platforms, and fetch install stats daily. The codebase follows a consistent architecture: each skill has a SKILL.md with YAML frontmatter, optional Python scripts following a credential → API wrapper → per-endpoint script pattern with TOON (Token-Oriented Object Notation) output, and dependencies declared between skills. While primarily an application, it has data-research characteristics due to its heavy use of external API scraping for market signals (Reddit, Twitter, ProductHunt) and SEO analytics. The repository is actively maintained with frequent releases, a changelog, and an agent-assisted development workflow (Ralph). Notable strengths include the reusable skill template pattern, cross-session memory via the archive skill, and the standalone SEO audit script. Key risks include reliance on multiple third-party API keys, tight coupling between some skills, and fragility in the install stats scraper.
GEO Optimizer is a Go library for Generative Engine Optimization that improves content visibility in AI search engines. It features a layered architecture with LLM abstraction, rule-based content scoring, and pluggable optimization strategies. The system optimizes content through a pipeline that applies strategies like structure enhancement, schema generation, and FAQ creation, using LLMs to generate optimized content while tracking improvements through scoring mechanisms. Key design patterns include the strategy interface for interchangeable optimizations and modular separation of concerns in the scoring system.
Polyglot is a Ruby gem that serves as a Jekyll plugin for internationalization (i18n) of static sites. It enables building a site in multiple languages by forking the Jekyll build process per language, patching core Jekyll classes (`Site`, `StaticFile`) to handle language-specific files, and providing Liquid tags for SEO headers (`I18n_Headers`) and URL relativization control (`static_href`). The plugin coordinates documents across languages, supports fallback to the default language, localizes `site.data` via language-specific subdirectories, and generates Netlify-compatible redirects. It is not a standalone application but a library that integrates deeply with Jekyll via hooks and monkey-patching. The repository includes a comprehensive demo site with 18 languages, a full RSpec test suite, CI via CircleCI, and extensive documentation in both README and `ai_docs/`. The codebase is well-structured, with clear separation of concerns (hooks, patches, liquid tags), and demonstrates non-trivial engineering in areas like parallel forking, regex-based URL relativization, and document coordination.
This repository operates as a static website (remotein.jp) that curates and displays a list of Japanese tech companies offering remote work. The core data source is two markdown tables in README.md (Japanese) and README.en.md (English). A Ruby script (`docs/upsert_data_by_readme.rb`) parses these tables, extracts company details (name, description, full-remote flag), generates Jekyll posts with front-matter and redirects, and produces bilingual search index JSON files. Jekyll builds the site using a custom theme with responsive design, dark mode, JSON-LD structured data for SEO, and client-side search via Simple-Jekyll-Search. The site is deployed via GitHub Pages with CI/CD through GitHub Actions. The architecture is a content pipeline: manual edits to README → script → Jekyll build → static hosting. There is no server-side logic or dynamic API. The repository is primarily a curation and presentation tool, not a software application in the traditional sense, but its automated data ingestion and site generation pipeline demonstrate solid engineering practices.
EasyInvoicePDF is a free, open-source, browser-based invoice generator that creates PDF invoices with live preview, no sign-up required, and no ads. Built with Next.js (App Router), React 19, TypeScript, Tailwind CSS, and shadcn/ui, it runs entirely client-side for the public editor—invoice data stays in localStorage and is never uploaded to a server. The application supports 10 languages, 120+ currencies, two PDF templates (default and Stripe-inspired), QR codes, multi-page PDFs, and shareable compressed URLs. A private server-side API (Bearer token + Upstash rate-limited) handles monthly recurring invoice generation via Trigger.dev cron, uploading PDFs to Google Drive, emailing via Resend, and sending Telegram notifications. The codebase also includes extensive SEO landing pages, a changelog, a founder page, and comprehensive testing (Vitest unit tests, Playwright e2e with PDF screenshot baselines). Architecture: The app uses two root layouts—unprefixed English-only routes (/) and locale-prefixed routes (/[locale]) for i18n via next-intl. The main invoice form is a large client component with react-hook-form and Zod validation, debounced autosave, and template/language switching. PDF rendering uses @react-pdf/renderer on the client for live preview and on the server for automation. External dependencies include Upstash Redis (rate limiting, queue), Resend (email), Google Drive (archive), Telegram (notifications), Sentry (error tracking), Umami (analytics), and Trigger.dev (scheduled tasks). The repository also contains a rich ecosystem of agent skills (Vercel React best practices, composition patterns, SEO audit, etc.) used in development workflows. Key data flows: User fills form → state stored in localStorage and optionally shared via compressed URL → PDF preview rendered client-side via @react-pdf/renderer → download or share. For monthly automation: Trigger.dev cron triggers server-side PDF generation → upload to Google Drive → email via Resend → Telegram notification. The backend API also supports a preview endpoint for sample PDFs and a Telegram webhook for on-demand generation.
This repository is a minimalist CV (resume) web application built with Next.js 16, React 19, TypeScript, and Tailwind CSS. It serves as a personal portfolio site that renders resume data from a single TypeScript file into a print-friendly layout. The architecture follows Next.js App Router conventions with server-side rendering and static generation. Key features include a command menu for quick navigation, responsive design, dark mode support, SEO-optimized structured data (JSON-LD), and a production-ready Docker setup. The codebase demonstrates strong engineering practices with clear separation of concerns, reusable UI components, and attention to accessibility and performance.
This repository is a personal blog and portfolio website built with Astro, Tailwind CSS, and Markdoc. It features a home page with project showcases, a blog with individual posts, a projects page, and an RSS feed. The site includes a dark mode toggle, SEO metadata generation, and custom Markdoc components for embedding media. The architecture follows Astro's standard structure with pages, layouts, and components, and uses a custom Markdoc setup for content processing.
Dante is a static site generator theme for Astro.js, designed for single-author blogs and portfolios. It provides a complete, production-ready setup with dark/light mode, responsive design, SEO metadata, RSS feed, sitemap, pagination, and a subscription form. The theme is built with Tailwind CSS v4 and uses Astro's content collections for Markdown-based blog posts, pages, and projects. Configuration is centralized in a single TypeScript file. The architecture follows Astro's SSG model with view transitions for a SPA-like experience. The codebase is well-structured, with reusable components and utility functions. It is a hybrid of a theme and a starter template, not a library or service.
Yoast SEO is a comprehensive WordPress SEO plugin providing on-page content analysis, XML sitemaps, schema markup generation, social media previews, and AI-assisted content optimization. The codebase is a monorepo containing PHP backend logic under a domain-driven architecture (Application, Domain, Infrastructure, User_Interface layers) and a modern JavaScript frontend using React, Redux, and Tailwind CSS. It integrates deeply with the WordPress ecosystem through hooks, REST API endpoints, and a robust conditional-based feature toggling system. Core capabilities include real-time readability and SEO assessments via a web worker-based analysis engine (packages/yoastseo), bulk editing of SEO metadata, AI content generation (titles, descriptions, outlines), schema aggregation for structured data, a dashboard with Google Site Kit integration, and extensive support for third-party plugins (WooCommerce, Elementor, WPML). The plugin employs a well-defined integration pattern (Integration_Interface with get_conditionals) for modular feature management. The repository exhibits professional engineering practices including comprehensive automated testing (PHPUnit, Jest, Mockery, Brain Monkey), dependency injection, and continuous integration. However, it shows signs of architectural drift with deprecated classes and legacy WPSEO_* namespaces coexisting with newer code, and a high open issue count reflecting its large user base. The AI features (consent management, content planner) are relatively recent additions with evolving requirements.
This repository is a Claude Code skill bundle for Generative Engine Optimization (GEO) and SEO auditing, distributed as an installable plugin. The core deliverable is a composite GEO Score (0-100) computed from six weighted categories: AI citability, brand authority, content E-E-A-T, technical health, structured data, and platform optimization. Users invoke slash commands such as /geo audit, /geo quick, /geo citability, /geo llmstxt, and /geo report, which orchestrate a set of skill definitions, agent prompts, and Python helper scripts to crawl external websites, analyze AI crawler accessibility, extract JSON-LD, generate llms.txt files, score content passages, and produce client-ready reports and proposals. It also includes a small Flask + HTMX CRM webapp for managing prospects and a white-label configuration system for agencies. The architecture is primarily a composition of markdown-based skills and agents with Python scripts as deterministic helpers. The main entry points are geo/SKILL.md (orchestrator), the scripts under scripts/, and the webapp at scripts/webapp/app.py. The system behaves as a productized agency service: it runs audits against arbitrary client domains, produces quantitative scores, generates branded PDF reports, pricing proposals, and monthly delta comparisons. Some research-oriented artifacts exist - cited market studies, scoring methodology documentation, and heuristic rubrics - but the dominant character is an application toolkit for practitioners rather than a data pipeline. Strengths include a clear JSON-to-stdout contract between scripts and skills, deterministic scoring modules such as citability_scorer.py and llmstxt_generator.py, reusable JSON-LD schema templates, and a sensible separation between deterministic checks and LLM-judged scoring. Weaknesses include documentation drift (inconsistent skill counts and command references), duplicated scoring rubrics in agent vs skill versions, a legacy ReportLab PDF pipeline documented alongside the newer pandoc/Chrome approach, and only narrow test coverage focused on fetch_page.py.
This is a monorepo containing starter templates and final code for the official Next.js Learn courses. It includes multiple independent Next.js applications demonstrating the Pages Router, App Router, data fetching, authentication, SEO optimization, and more. The code is educational, well-structured, and follows modern Next.js patterns (server actions, streaming, suspense, etc.). It is not a production application but serves as a reference implementation for learning. The dashboard example includes a full CRUD invoice management system with PostgreSQL, NextAuth authentication, and Tailwind CSS styling. The basics examples cover static generation, dynamic routes, API routes, and TypeScript. The SEO example demonstrates performance optimization techniques like dynamic imports and lazy loading.
This repository is a comprehensive, structured library of over 50 marketing 'skills' designed for AI coding agents (Claude Code, Codex, Cursor, etc.). Each skill is a self-contained directory with a SKILL.md (frontmatter + workflow), a references/ folder with deep-dive documentation and benchmarks, and evals/evals.json for behavioral testing. The skills cover the full marketing lifecycle: copywriting, SEO, paid ads (Meta, Google, LinkedIn), email, social, CRO, pricing, offers, attribution, market research, and more. Additionally, the repository includes 40+ zero-dependency Node.js CLI scripts that act as API clients for marketing tools like Ahrefs, Semrush, GA4, Meta Ads, Mailchimp, etc., each following a consistent pattern with dry-run support and environment variable authentication. Several integration guides and a central tool registry (REGISTRY.md) complete the ecosystem. While primarily a content library, the CLI scripts and validation/sync tooling demonstrate strong engineering patterns. The skills are designed to be consumed by AI agents to execute complex, multi-step marketing tasks, with cross-skill references and a shared context document (product-marketing.md) enabling orchestration.
This repository is a comprehensive, community-maintained reference guide for HTML `<head>` elements. It catalogs recommended meta tags, link relations, social media integration (Open Graph, Schema.org, Fediverse), browser-specific tags (iOS, Android, Chinese browsers), and deprecated elements. The project is purely documentation—not a software application, library, or data pipeline. It is widely used (over 30k stars) and actively maintained, with a GitHub Actions workflow that syncs the README to a GitHub Pages site (htmlhead.dev). The codebase consists of a single markdown file (README.md) and a deprecated elements file (DEPRECATED.md), plus a CI workflow. There are no executable components, tests, or reusable software modules. The value lies in its curated, up-to-date reference for web developers.
This repository is primarily a curated knowledge base and personal reference collection (a 'second brain') organized into dozens of markdown files across categories such as coding languages, blockchain, operating systems, trading, and general utilities. Each markdown file contains tables of contents and extensive lists of external links to tools, libraries, tutorials, and best practices. The repository also includes a small set of utility scripts (e.g., remark.js for auto-generating table of contents, wip-dedupe.js for deduplication, shell migration scripts, and code snippets) and an Obsidian vault configuration. While not a traditional application, the automation scripts add a thin layer of tooling around the curated content. The primary value is as a discovery index for developers and researchers, but the code itself is minimal and tightly coupled to personal workflow, limiting reuse.