[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-93297":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":14,"subscribersCount":14,"size":14,"stars1d":14,"stars7d":15,"stars30d":15,"stars90d":14,"forks30d":14,"starsTrendScore":16,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":18,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":21,"hasPages":19,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":14,"starSnapshotCount":14,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},93297,"beautify-github-readme","oil-oil\u002Fbeautify-github-readme","oil-oil","Design clear, theme-specific GitHub README homepages with SVG titles, real proof, and maintainable Markdown",null,"Python",837,47,107,0,730,45,79.04,"MIT License",false,"main",true,[23,24,25,26,27],"agent-skill","codex-skill","github-readme","readme-design","svg","2026-07-22 04:02:08","\u003Cp align=\"right\">\n  \u003Cstrong>English\u003C\u002Fstrong> · \u003Ca href=\".\u002FREADME.zh-CN.md\">简体中文\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fhero.svg\" width=\"100%\" alt=\"Beautify GitHub README: help visitors understand a repository at first glance.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Ftheme-wall.svg\" width=\"100%\" alt=\"Six project-native README directions for developer tools, AI products, design resources, research, creator projects, and open-source libraries.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fsection-used-by.svg\" width=\"100%\" alt=\"Real repositories already using beautify-github-readme.\">\n\u003C\u002Fp>\n\nThese are not hypothetical templates. The method is already used by four public repositories, each with its own visual language and content structure:\n\n- **[oil-ppt](https:\u002F\u002Fgithub.com\u002Foil-oil\u002Foil-ppt)** — presents the method, results, and first-use path for programmatic slide creation in one visual system.\n- **[draw-ui](https:\u002F\u002Fgithub.com\u002Foil-oil\u002Fdraw-ui)** — uses real UI outputs to explain the path from a brief and reference images to HTML\u002FCSS reconstruction.\n- **[oil-icon](https:\u002F\u002Fgithub.com\u002Foil-oil\u002Foil-icon)** — uses real icon sets to explain style locking, batch generation, slicing, and transparent delivery.\n- **[Selector](https:\u002F\u002Fgithub.com\u002Foil-oil\u002Fselector)** — puts page selection, structured context, and real output directly into the opening screen and examples.\n- **[torqueDASH-Next](https:\u002F\u002Fgithub.com\u002Fmoesix\u002Ftorque-dash-next)** — uses a project-native SVG hero with OBD-II PID data and a real dashboard screenshot to explain a self-hosted vehicle telemetry dashboard.\n\nIf this Skill helped you create a public README you are proud of, you are welcome to propose it for this list in a PR. This is completely optional: the footer signature is appreciated but never required, and showcase submissions remain subject to maintainer review.\n\nBelow are four independent hero directions. They do not share one house style; each derives its typography, color, composition, and proof from the project itself.\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fcase-kubernetes.svg\" width=\"100%\" alt=\"Kubernetes README hero example with a black system layout and cluster relationship diagram.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fcase-pytorch.svg\" width=\"100%\" alt=\"PyTorch README hero example with a warm white background and neural-network paths.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fcase-postgresql.svg\" width=\"100%\" alt=\"PostgreSQL README hero example with a deep blue editorial layout and relational tables.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fcase-rust.svg\" width=\"100%\" alt=\"Rust README hero example with industrial typography and code structure.\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fsection-why.svg\" width=\"100%\" alt=\"01 Make the project clear before asking people to keep reading.\">\n\u003C\u002Fp>\n\nMost repositories already contain enough information. The problem is usually the order: visitors see internal terminology, installation commands, and directory trees before they understand what the project is for.\n\n`beautify-github-readme` reads the real repository first, identifies the clearest value and proof, and only then decides how the page should look.\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fbefore-after.svg\" width=\"100%\" alt=\"A README changing from dense information with no clear entry point to a value, proof, method, and first-use sequence.\">\n\u003C\u002Fp>\n\nIn whole-README mode, it works across three layers:\n\n| Content | Visual system | Engineering |\n| --- | --- | --- |\n| Remove repetition, move proof forward, and replace internal jargon with concrete outcomes | Derive color, typography, composition, and project-native motifs before designing the hero and supporting modules | Keep assets GitHub-safe, images accessible, commands copyable, and body text searchable |\n\nDifferent projects should not receive the same template. A CLI can use command rhythm and cursors; an icon system can use keylines and cutouts; a research repository can use coordinates, charts, and evidence labels.\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fsection-method.svg\" width=\"100%\" alt=\"02 Put visual identity in SVG and readable content in Markdown.\">\n\u003C\u002Fp>\n\nGitHub READMEs do not have the layout freedom of a website. This Skill separates the visual and content layers:\n\n- SVG handles the hero, section transitions, comparisons, diagrams, and identity.\n- PNG\u002FWebP handles screenshots, generated artwork, and complex showcase walls.\n- Markdown handles explanations, commands, links, configuration, and contribution details.\n\nThe result can feel designed without becoming one long image that nobody can search, copy, or maintain.\n\nThe reusable production guidance lives here:\n\n- [Designing a project-native hero](.\u002Fskills\u002Fbeautify-github-readme\u002Freferences\u002Fproject-native-hero.md)\n- [Writing GitHub-safe README SVGs](.\u002Fskills\u002Fbeautify-github-readme\u002Freferences\u002Fsvg-production.md)\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fworkflow.svg\" width=\"100%\" alt=\"Understand the project, set the direction, structure the content, build the visuals, and review the preview.\">\n\u003C\u002Fp>\n\nThe process keeps three promises: use real project material, never invent capabilities, and never publish without explicit approval.\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\".\u002Fassets\u002Freadme\u002Fen\u002Fsection-use.svg\" width=\"100%\" alt=\"03 Send the repository to your Agent.\">\n\u003C\u002Fp>\n\n**Option 1 · Install from the command line**\n\n```bash\nnpx skills add oil-oil\u002Fbeautify-github-readme\n```\n\n**Option 2 · Ask your Agent to install it**\n\n```text\nInstall this Skill: https:\u002F\u002Fgithub.com\u002Foil-oil\u002Fbeautify-github-readme\n```\n\nThe Skill has two explicit modes:\n\n| Mode | What it changes | What it leaves alone by default |\n| --- | --- | --- |\n| Whole README | Reading order, copy hierarchy, proof, Markdown, and the complete visual system | It will not commit, push, or publish without approval |\n| SVG-only | A hero, section headers, workflow, badge, diagram, or coordinated SVG asset set | It will not edit README copy, order, image references, or links |\n\nIf the request already states the scope, the Skill starts directly. If a user only says “beautify this repository” or provides a repository URL, the Agent asks:\n\n```text\nWould you like me to improve the whole README or only create SVG decorations?\nIf SVG-only, do you need a hero, section headers, workflow, badge, or a coordinated asset set?\n```\n\n**Whole-README mode**\n\n```text\nUse $beautify-github-readme to redesign this repository homepage around its real project theme.\nShow me a local preview first and do not push anything.\n```\n\n**SVG-only mode**\n\n```text\nUse $beautify-github-readme to keep the README unchanged and create one SVG hero plus three section headers.\nDerive the style from the existing project and show me rendered previews first.\n```\n\nReading a README for context does not grant permission to edit it. In SVG-only mode, embedding the new assets requires a separate, explicit approval.\n\nYou can also request a read-only audit:\n\n```text\nUse $beautify-github-readme to audit this README for clarity, hierarchy, trust, and maintenance cost. Do not edit files.\n```\n\nWhole-README mode delivers a local preview, visual assets, and a README diff. SVG-only mode delivers the SVG files, rendered previews, and optional embed snippets. Commits, pushes, PRs, and publishing always require explicit authorization.\n\nMIT License\n\n---\n\nThis README is also a working example: it combines a project-native hero, a theme wall, real adoption proof, section transitions, and readable Markdown instead of rasterizing the whole page.\n","这是一个为 GitHub 仓库 README 提供主题化、可视化增强的工具，支持生成与项目特性深度契合的 SVG 标题、真实成果展示和结构清晰的 Markdown 页面。核心特点是基于项目自身内容（如技术栈、输出物、领域特征）自动生成风格统一且信息明确的首页视觉系统，而非通用模板；采用 Python 实现，强调可维护性与语义真实性。适用于开源库、AI 工具、设计资源、研究项目等需快速传达核心价值与使用路径的技术型仓库。",2,"2026-07-15 02:30:11","CREATED_QUERY"]