[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW9XPS15DNWF8KP9K3RWJC":3,"skill-same:01M6JW9XPS15DNWF8KP9K3RWJC":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6JW9XPS15DNWF8KP9K3RWJC","alignment-text-and-numerics",null,"Use this skill when designing text-alignment and numeric-alignment decisions — choosing between left, right, center, and justified text; right-aligning numeric columns in tables; aligning labels relative to inputs; handling decimal alignment for currency. Trigger when laying out body content, designing tables with mixed types, or fixing alignment issues in dense data displays. Sub-aspect of `alignment`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Falignment-text-and-numerics\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"alignment text and numerics","text","alignment","trigger","when","body","labels","for","tables","with","types","columns","issues","currency","use","read","decisions","first","data","content","2026-11-10 10:12:30",false,"---\nname: alignment-text-and-numerics\ndescription: 'Use this skill when designing text-alignment and numeric-alignment decisions — choosing between left, right, center, and justified text; right-aligning numeric columns in tables; aligning labels relative to inputs; handling decimal alignment for currency. Trigger when laying out body content, designing tables with mixed types, or fixing alignment issues in dense data displays. Sub-aspect of `alignment`; read that first.'\n---\n\n# Text and numeric alignment\n\nText and numbers behave differently. Text wants to flow naturally, with predictable left edges so the eye can return to a known column. Numbers want to align by digit position so the user can compare magnitudes. Mixing them in a table requires deliberate alignment per column.\n\n## Text alignment\n\n### Left-aligned (the default for body)\n\nIn LTR scripts, body text should almost always be left-aligned. The reasons:\n\n- **Predictable left edge** — the eye returns to a known x-position on each line.\n- **Ragged-right edge** — variations in line length signal where each line ends.\n- **No \"rivers\" of white space** that justified text creates.\n\nBest for: paragraphs, descriptions, body copy, lists, captions.\n\n### Right-aligned\n\nUsed in narrow contexts:\n\n- **Numeric columns in tables** so digit positions stack.\n- **Labels in two-column forms** (label-flush-right, input-flush-left) so the gap between label and input is consistent regardless of label length.\n- **Some footer text** in mixed-direction layouts.\n- **Content in RTL scripts** (Arabic, Hebrew) — the equivalent of left-aligned in LTR.\n\nAvoid for body content in LTR scripts.\n\n### Center-aligned\n\nUse *sparingly* and only for short content:\n\n- **Hero headlines** (one line, focal point).\n- **Page titles** above content.\n- **Button labels** (centered within the button).\n- **Single-line CTAs** (\"Sign up below\" → button).\n- **Quotations or epigraphs**.\n\nAvoid for paragraphs of body text. Center-aligned body is significantly slower to read because each line starts at a different x-position.\n\n### Justified (both edges flush)\n\nUsed in print where typesetting can hyphenate and adjust spacing precisely. On screens:\n\n- **Without hyphenation**: don't. The \"rivers\" of white space between widely-spaced words are distracting.\n- **With CSS `hyphens: auto`**: acceptable for long-form prose, particularly in narrow columns.\n\nMost modern web design uses ragged-right (left-aligned) by default.\n\n## Numeric alignment\n\n### Right-align all numeric columns\n\nNumbers should right-align so that digit positions stack:\n\n```\n        1.00\n       12.50\n      135.00\n    9,876.50\n```\n\nThe eye scans the right edge to compare magnitudes. Left-aligned, the same numbers don't compare:\n\n```\n1.00\n12.50\n135.00\n9,876.50\n```\n\nNow the user has to read each number to compare; the columnar advantage is lost.\n\n### Use tabular numerals (`font-variant-numeric: tabular-nums`)\n\nMost fonts ship with proportional numerals (each digit has slightly different width — `1` is narrower than `8`). For columns of numbers, this means digit positions don't quite stack even when right-aligned. Use tabular numerals instead:\n\n```css\n.numeric-column {\n  text-align: right;\n  font-variant-numeric: tabular-nums;\n}\n```\n\nNow every digit occupies the same width; columns align perfectly.\n\n### Decimal alignment\n\nWhen numbers have varying decimal places, you sometimes want to align *on the decimal point* rather than the right edge. CSS doesn't make this easy; the workarounds:\n\n- **Force consistent decimal places** (\"$2.50\" not \"$2.5\") so right-alignment serves as decimal alignment.\n- **Use a span around the integer part** and another around the decimal, with explicit width on the integer part. Fragile; reserve for cases where it matters.\n\nFor most products, forcing consistent decimal places is the simpler answer.\n\n### Currency\n\nDisplay currency with locale-appropriate symbol position and separators:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' }).format(1234.5);\n\u002F\u002F \"$1,234.50\"\n\nnew Intl.NumberFormat('de-DE', { style: 'currency', currency: 'EUR' }).format(1234.5);\n\u002F\u002F \"1.234,50 €\"\n```\n\nRight-align currency columns; use tabular numerals.\n\n## Label-input alignment\n\nThree common patterns:\n\n### Top-aligned labels (most common in vertical forms)\n\nLabel sits above input. No alignment between label and input axis (they're stacked vertically).\n\n```html\n\u003Clabel for=\"email\">Email\u003C\u002Flabel>\n\u003Cinput id=\"email\" type=\"email\" \u002F>\n```\n\nPros: simplest; works at any width; labels can be long without affecting layout.\n\n### Right-aligned labels (label-input pairs in two columns)\n\nLabel flush-right against input flush-left. The gap between is consistent regardless of label length.\n\n```html\n\u003Cstyle>\n  .field-row { display: grid; grid-template-columns: 8rem 1fr; gap: 12px 16px; }\n  .field-row label { text-align: right; padding-top: 0.5rem; }\n\u003C\u002Fstyle>\n\n\u003Cdiv class=\"field-row\">\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" \u002F>\n\u003C\u002Fdiv>\n```\n\nPros: scannable for dense settings; predictable column widths.\nCons: label width must accommodate the longest label; long labels look awkward right-aligned.\n\n### Left-aligned labels (label-input pairs)\n\nBoth label and input left-aligned in their columns. The gap between label and input varies with label length, creating a slight visual ragged edge.\n\nPros: more relaxed; easier to read longer labels.\nCons: less scannable; the variable gap reads as messier.\n\nFor most app settings: top-aligned labels. For compact dense forms: right-aligned. Left-aligned columnar is a third choice that some prefer aesthetically.\n\n## Anti-patterns\n\n- **Centered body text.** Reading speed drops 30%+ for centered paragraphs.\n- **Left-aligned numeric columns.** Magnitudes can't be compared.\n- **Mixed proportional + tabular numerals across a single column.** Drift accumulates.\n- **Inconsistent decimal places.** \"$2\", \"$2.5\", \"$2.50\" in the same column. Right-alignment doesn't save it.\n- **Justified body text without hyphenation.** Rivers of white space.\n- **Centering headers but not body** without a clear reason. The reading rhythm jumps.\n- **Mixing label alignment within a form.** Some labels left, some right, some top. Each switch is a re-orientation.\n\n## Heuristics\n\n1. **The numeric-comparison test.** Look down a numeric column. Can you spot the largest value at a glance? If not, alignment is wrong.\n2. **The reading-speed test.** Read centered body text vs. left-aligned. Notice the cognitive cost. (Then never use centered body again.)\n3. **The label-alignment audit.** Across the form, are all labels aligned the same way? If not, fix.\n4. **The currency precision test.** All currency in a column has the same decimal places. If \"$2.5\" sits next to \"$1,234.00\", fix the precision.\n\n## Related sub-skills\n\n- **`alignment`** (parent).\n- **`alignment-grid-systems`** — the structural grid that text and numbers align within.\n- **`legibility`** and **`readability`** — typography decisions interact with alignment.\n- **`proximity-data-tables`** — table-specific alignment patterns.\n\n## Resources\n\n- **Bringhurst, R.** *The Elements of Typographic Style* — comprehensive reference on text alignment in typography.\n- **Tufte, E.** *The Visual Display of Quantitative Information* — alignment in tabular data.\n- **Material Design \u002F Apple HIG** — both document text and numeric alignment conventions.\n","# Text and numeric alignment\n\nText and numbers behave differently. Text wants to flow naturally, with predictable left edges so the eye can return to a known column. Numbers want to align by digit position so the user can compare magnitudes. Mixing them in a table requires deliberate alignment per column.\n\n## Text alignment\n\n### Left-aligned (the default for body)\n\nIn LTR scripts, body text should almost always be left-aligned. The reasons:\n\n- **Predictable left edge** — the eye returns to a known x-position on each line.\n- **Ragged-right edge** — variations in line length signal where each line ends.\n- **No \"rivers\" of white space** that justified text creates.\n\nBest for: paragraphs, descriptions, body copy, lists, captions.\n\n### Right-aligned\n\nUsed in narrow contexts:\n\n- **Numeric columns in tables** so digit positions stack.\n- **Labels in two-column forms** (label-flush-right, input-flush-left) so the gap between label and input is consistent regardless of label length.\n- **Some footer text** in mixed-direction layouts.\n- **Content in RTL scripts** (Arabic, Hebrew) — the equivalent of left-aligned in LTR.\n\nAvoid for body content in LTR scripts.\n\n### Center-aligned\n\nUse *sparingly* and only for short content:\n\n- **Hero headlines** (one line, focal point).\n- **Page titles** above content.\n- **Button labels** (centered within the button).\n- **Single-line CTAs** (\"Sign up below\" → button).\n- **Quotations or epigraphs**.\n\nAvoid for paragraphs of body text. Center-aligned body is significantly slower to read because each line starts at a different x-position.\n\n### Justified (both edges flush)\n\nUsed in print where typesetting can hyphenate and adjust spacing precisely. On screens:\n\n- **Without hyphenation**: don't. The \"rivers\" of white space between widely-spaced words are distracting.\n- **With CSS `hyphens: auto`**: acceptable for long-form prose, particularly in narrow columns.\n\nMost modern web design uses ragged-right (left-aligned) by default.\n\n## Numeric alignment\n\n### Right-align all numeric columns\n\nNumbers should right-align so that digit positions stack:\n\n```\n        1.00\n       12.50\n      135.00\n    9,876.50\n```\n\nThe eye scans the right edge to compare magnitudes. Left-aligned, the same numbers don't compare:\n\n```\n1.00\n12.50\n135.00\n9,876.50\n```\n\nNow the user has to read each number to compare; the columnar advantage is lost.\n\n### Use tabular numerals (`font-variant-numeric: tabular-nums`)\n\nMost fonts ship with proportional numerals (each digit has slightly different width — `1` is narrower than `8`). For columns of numbers, this means digit positions don't quite stack even when right-aligned. Use tabular numerals instead:\n\n```css\n.numeric-column {\n  text-align: right;\n  font-variant-numeric: tabular-nums;\n}\n```\n\nNow every digit occupies the same width; columns align perfectly.\n\n### Decimal alignment\n\nWhen numbers have varying decimal places, you sometimes want to align *on the decimal point* rather than the right edge. CSS doesn't make this easy; the workarounds:\n\n- **Force consistent decimal places** (\"$2.50\" not \"$2.5\") so right-alignment serves as decimal alignment.\n- **Use a span around the integer part** and another around the decimal, with explicit width on the integer part. Fragile; reserve for cases where it matters.\n\nFor most products, forcing consistent decimal places is the simpler answer.\n\n### Currency\n\nDisplay currency with locale-appropriate symbol position and separators:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' }).format(1234.5);\n\u002F\u002F \"$1,234.50\"\n\nnew Intl.NumberFormat('de-DE', { style: 'currency', currency: 'EUR' }).format(1234.5);\n\u002F\u002F \"1.234,50 €\"\n```\n\nRight-align currency columns; use tabular numerals.\n\n## Label-input alignment\n\nThree common patterns:\n\n### Top-aligned labels (most common in vertical forms)\n\nLabel sits above input. No alignment between label and input axis (they're stacked vertically).\n\n```html\n\u003Clabel for=\"email\">Email\u003C\u002Flabel>\n\u003Cinput id=\"email\" type=\"email\" \u002F>\n```\n\nPros: simplest; works at any width; labels can be long without affecting layout.\n\n### Right-aligned labels (label-input pairs in two columns)\n\nLabel flush-right against input flush-left. The gap between is consistent regardless of label length.\n\n```html\n\u003Cstyle>\n  .field-row { display: grid; grid-template-columns: 8rem 1fr; gap: 12px 16px; }\n  .field-row label { text-align: right; padding-top: 0.5rem; }\n\u003C\u002Fstyle>\n\n\u003Cdiv class=\"field-row\">\n  \u003Clabel for=\"email\">Email\u003C\u002Flabel>\n  \u003Cinput id=\"email\" \u002F>\n\u003C\u002Fdiv>\n```\n\nPros: scannable for dense settings; predictable column widths.\nCons: label width must accommodate the longest label; long labels look awkward right-aligned.\n\n### Left-aligned labels (label-input pairs)\n\nBoth label and input left-aligned in their columns. The gap between label and input varies with label length, creating a slight visual ragged edge.\n\nPros: more relaxed; easier to read longer labels.\nCons: less scannable; the variable gap reads as messier.\n\nFor most app settings: top-aligned labels. For compact dense forms: right-aligned. Left-aligned columnar is a third choice that some prefer aesthetically.\n\n## Anti-patterns\n\n- **Centered body text.** Reading speed drops 30%+ for centered paragraphs.\n- **Left-aligned numeric columns.** Magnitudes can't be compared.\n- **Mixed proportional + tabular numerals across a single column.** Drift accumulates.\n- **Inconsistent decimal places.** \"$2\", \"$2.5\", \"$2.50\" in the same column. Right-alignment doesn't save it.\n- **Justified body text without hyphenation.** Rivers of white space.\n- **Centering headers but not body** without a clear reason. The reading rhythm jumps.\n- **Mixing label alignment within a form.** Some labels left, some right, some top. Each switch is a re-orientation.\n\n## Heuristics\n\n1. **The numeric-comparison test.** Look down a numeric column. Can you spot the largest value at a glance? If not, alignment is wrong.\n2. **The reading-speed test.** Read centered body text vs. left-aligned. Notice the cognitive cost. (Then never use centered body again.)\n3. **The label-alignment audit.** Across the form, are all labels aligned the same way? If not, fix.\n4. **The currency precision test.** All currency in a column has the same decimal places. If \"$2.5\" sits next to \"$1,234.00\", fix the precision.\n\n## Related sub-skills\n\n- **`alignment`** (parent).\n- **`alignment-grid-systems`** — the structural grid that text and numbers align within.\n- **`legibility`** and **`readability`** — typography decisions interact with alignment.\n- **`proximity-data-tables`** — table-specific alignment patterns.\n\n## Resources\n\n- **Bringhurst, R.** *The Elements of Typographic Style* — comprehensive reference on text alignment in typography.\n- **Tufte, E.** *The Visual Display of Quantitative Information* — alignment in tabular data.\n- **Material Design \u002F Apple HIG** — both document text and numeric alignment conventions.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Falignment-text-and-numerics",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alignment-text-and-numerics",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alignment-text-and-numerics",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill alignment-text-and-numerics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Falignment-text-and-numerics\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftypography-alignment-reference.md","REFERENCE","参考文档",3879,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Falignment-text-and-numerics\u002Freferences\u002Ftypography-alignment-reference.md",[75,83,90,97,123,146],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":82},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":82},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[104,105,106,107,108,109,110,111,112,113,114,23,115,116,117,118,119,120,121,122],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":39},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[130,131,132,118,28,133,134,135,136,137,138,35,139,140,109,141,142,143,144,145],"deja reflect","reflect","review","record","github","next","https","node","Rules","brew","remember","project rules","project","session","end","reflection",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":163,"publishedAt":39},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[152,157,160],{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":158,"categoryName":159,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":161,"categoryName":162,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000010","后端与接口",[148,164,165,166,167,168,169,142,170,110,171,172,173,174,23,175,176,177,178,179],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]