Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/a-master-artificer/llms.txt

Use this file to discover all available pages before exploring further.

The Skills page gives visitors a structured view of what you know and what you work with. In the A Master Artificer theme, it maps to the route /skills and carries the themed navigation label Athenaeum. The file responsible for it is skills.html at the repository root, and its companion JavaScript module is assets/Skills.js, which holds the skills categories, individual items, and any visual presentation logic. While the Projects page shows your skills in action, the Athenaeum page gives a visitor the explicit list — languages, frameworks, tools, platforms, and capabilities. A well-organized skills section helps potential collaborators or employers quickly confirm that your background aligns with what they are looking for. The goal is clarity: make it easy to scan, easy to understand, and honest about your actual level of experience with each item.

​
File

skills.html
Route: /skills
Themed label: Athenaeum
Asset: assets/Skills.js

​
HTML Structure

skills.html shares the same HTML shell as every other page in the theme. The skills content is rendered by the React application from assets/Skills.js. The HTML file loads the shared bundle and provides the <div id="root"> mount point. 
<!doctype html>
<html lang="en">

<head>
    <meta charset="UTF-8" />
    <link rel="icon" type="image/svg+xml" href="./vite.svg" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <title>A Master Artificer</title>
    <script type="module" crossorigin src="./assets/main.js"></script>
    <link rel="modulepreload" crossorigin href="./assets/proxy.js">
    <link rel="modulepreload" crossorigin href="./components/grimoire/AstrolabeNav.js">
    <link rel="modulepreload" crossorigin href="./components/grimoire/CustomCursor.js">
    <link rel="stylesheet" crossorigin href="./assets/main.css">
</head>

<body>
    <div id="root"></div>
</body>

</html>

​
What to Edit

Open assets/Skills.js and replace the sample skills data with your own. Skills are typically organized into categories, with individual items listed inside each category.
1

Identify your skill categories

Group related skills before editing the file. Common groupings include programming languages, frameworks and libraries, tools and platforms, databases, design tools, and soft skills. Use the categories that make the most sense for your background — there is no required structure.
2

Replace the sample skills with your own

Work through each category in assets/Skills.js and replace the placeholder items with your actual skills. Only list skills you are genuinely comfortable discussing in an interview or applying in a project.
3

List languages and runtimes

Include the programming languages you work in regularly. If you have a primary language, list it first within its category. Include runtimes and environments where relevant — for example, Node.js belongs alongside JavaScript.
4

List frameworks and libraries

Include the frameworks and libraries that are central to your work. Frameworks change more quickly than languages, so keep this section current. Remove items you have not used in a meaningful project.
5

List tools, platforms, and services

Version control, deployment platforms, CI/CD tools, cloud services, databases, editors, and design applications all belong here. Separate them into subcategories if the list becomes long enough to be hard to scan.
6

Update the page title

In skills.html, update the <title> tag to include your name and the page context — for example, Your Name — Skills.

​
Organizing Skills Effectively

A skills list that is too long dilutes the signal. A skills list that is too short makes it hard to assess fit. The goal is a list that is complete enough to be useful but focused enough to stay readable. A few principles that help:
  • List skills you can defend. Every item on the page is an implicit offer to answer questions about it. If you list a technology you used once in a tutorial, be ready to explain that honestly if someone asks.
  • Group by how you actually use them. If you use JavaScript for both frontend and backend work, it does not matter which category it lands in — put it where a visitor scanning the page will find it first.
  • Keep the list current. A skills page that lists technologies from several years ago with no current additions suggests the portfolio has not been maintained. Update it when you learn something new and remove items that no longer represent your actual capabilities.
  • Avoid inflating proficiency labels. If your skills section uses proficiency indicators, be conservative. Labeling everything as “expert” makes the labels meaningless. A smaller set of things you genuinely know well is more credible than a long list with overstated confidence levels.

Build docs developers (and LLMs) love

Get started for freeTalk to us