Project-Arcturus
Like a little project arcturus.
Install / Use
npx skills add nicholasgalante1997/Project-ArcturusInstalls into whichever agent you are using.
Amazon Q Rules
Amazon Q Developer rules
Quality Score
Category
DesignSupported Platforms
Our assessment of Project-Arcturus
Project-Arcturus scores 62/100 on our quality scale, 176th of 194 Design skills we index.
Its Amazon Q Rules is 7.6 KB long, well organised into 17 sections with 12 code examples: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-09-27 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
Project-Arcturus compared with similar skills
All 4 of these similar skills score higher than Project-Arcturus; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| Project-Arcturus (this skill)by nicholasgalante1997 | 62 | 0 | — | Amazon Q Rules |
| designby nextlevelbuilder | 100 | 130.2k | 6d ago | SKILL.md |
| ui-ux-pro-maxby nextlevelbuilder | 100 | 130.2k | 6d ago | SKILL.md |
| design-isby thedotmack | 100 | 94.6k | 3d ago | SKILL.md |
| dotnet-backend-patternsby wshobson | 100 | 39.9k | 6d ago | SKILL.md |
Frequently asked questions
- How do I install Project-Arcturus?
- Run
npx skills add nicholasgalante1997/Project-Arcturus. The install tabs above show the steps for each supported agent. - Which AI agents does Project-Arcturus work with?
- It is written for Amazon Q, as a Amazon Q Rules file. Other agents that read the same format can often use it too.
- Is Project-Arcturus safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is Project-Arcturus still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubVoid Design System Rules
Purpose
Define standards for extending and implementing components in the Void design system.
Priority
High
Instructions
Component Architecture
ALWAYS follow component composition patterns from .amazonq/rules/frontend/component-patterns.md (ID: FOLLOW_COMPOSITION)
ALWAYS implement components in React with TypeScript (ID: REACT_TS)
ALWAYS separate Container and View components (ID: SEPARATE_CONCERNS)
Styling Standards
NEVER use CSS-in-JS solutions (styled-components, emotion, Material-UI) (ID: NO_CSS_IN_JS)
ALWAYS use vanilla CSS with CSS variables from @arcjr/void-tokens (ID: VANILLA_CSS)
ALWAYS use clsx for conditional classes (ID: USE_CLSX)
// Good - using clsx
import clsx from 'clsx';
const className = clsx(
'void-button',
variant && `void-button--${variant}`,
disabled && 'void-button--disabled'
);
ALWAYS reference CSS variables from void-tokens (ID: VOID_CSS_VARS)
.void-button {
background-color: var(--color-brand-azure);
padding: var(--spacing-3) var(--spacing-5);
border-radius: var(--border-radius-md);
transition: all var(--transition-duration-fast) var(--transition-easing-ease);
}
NEVER import React in View components when using automatic JSX runtime (ID: NO_REACT_IMPORT_VIEWS)
// Good
import { memo } from 'react';
// Bad
import React, { memo } from 'react';
Component Documentation
ALWAYS include JSDoc comments in Component.tsx explaining (ID: JSDOC_REQUIRED):
- Component purpose and use cases
- Best practice usage patterns
- Examples of common scenarios
/**
* Button component for user interactions
*
* @example
* // Primary button
* <Button variant="primary" onClick={handleClick}>
* Click me
* </Button>
*
* @example
* // Disabled state
* <Button disabled>
* Cannot click
* </Button>
*/
Storybook Integration
ALWAYS create Storybook CSF files co-located with components (ID: STORYBOOK_COLOCATED)
ALWAYS import component CSS in story files (ID: IMPORT_CSS_IN_STORIES)
// Button.stories.tsx
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './index';
import './Button.css'; // Import CSS in story file
const meta: Meta<typeof Button> = {
title: 'Void/Button',
component: Button,
tags: ['autodocs']
};
ALWAYS format stories with proper meta, args, and multiple variants (ID: WELL_FORMATTED_STORIES)
ALWAYS include stories for all component states and variants (ID: COMPREHENSIVE_STORIES)
File Structure
ALWAYS organize Void components following this structure (ID: VOID_STRUCTURE):
packages/void-components/src/Button/
├── index.ts # Barrel export
├── Component.tsx # Container with JSDoc
├── View.tsx # Presentational
├── types.ts # TypeScript types
├── Button.css # Vanilla CSS with Void variables
├── Button.stories.tsx # Storybook stories (imports CSS)
└── __tests__/
└── Button.test.tsx # Bun tests
CSS Organization
NEVER import CSS files directly into .tsx files except in .stories.tsx files (ID: NO_CSS_IMPORTS_TSX)
ALWAYS create separate CSS files for components (ID: SEPARATE_CSS)
ALWAYS use BEM-style naming with void- prefix (ID: VOID_BEM)
.void-button { }
.void-button--primary { }
.void-button--disabled { }
.void-button__icon { }
Build System
ALWAYS use Bun.build() programmatic API for bundling (ID: BUN_BUILD_API)
ALWAYS use separate functions for JS and CSS bundling (ID: SEPARATE_BUNDLE_FNS)
ALWAYS run type checking with tsc and tsc-alias after bundling (ID: TSC_AFTER_BUNDLE)
// build.ts pattern
async function bundle() {
const result = await Bun.build({
entrypoints: ['./src/index.ts'],
outdir: './dist',
target: 'browser',
format: 'esm',
sourcemap: 'external',
minify: false,
splitting: false,
external: ['react', 'react-dom']
});
}
async function bundleCSS() {
const cssFiles = new Bun.Glob('src/**/*.css');
const cssContent: string[] = [];
for await (const file of cssFiles.scan('.')) {
const content = await Bun.file(file).text();
cssContent.push(`/* ${file} */\n${content}\n`);
}
await Bun.write('dist/index.css', cssContent.join('\n'));
}
Package Configuration
ALWAYS use modern "files" and "exports" fields in package.json (ID: MODERN_PKG_JSON)
ALWAYS set "type": "module" (ID: TYPE_MODULE)
ALWAYS export both JS and CSS in exports field (ID: EXPORT_JS_CSS)
{
"type": "module",
"files": ["dist"],
"exports": {
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.js"
},
"./styles": "./dist/index.css",
"./package.json": "./package.json"
}
}
Storybook Configuration
ALWAYS use Vite aliases to resolve workspace packages (ID: VITE_ALIASES)
// .storybook/main.ts
viteFinal: async (config) => {
config.resolve.alias = {
'@arcjr/void-tokens': resolve(__dirname, '../../void-tokens'),
'@arcjr/void-css': resolve(__dirname, '../../void-css')
};
return config;
}
ALWAYS import void-tokens CSS in preview.ts (ID: TOKENS_IN_PREVIEW)
// .storybook/preview.ts
import '@arcjr/void-tokens/dist/css/void-tokens.css';
Testing
ALWAYS use Bun test runner with happy-dom (ID: BUN_TEST_HAPPYDOM)
ALWAYS use @testing-library/react for component tests (ID: TESTING_LIBRARY)
ALWAYS test accessibility attributes (aria-*, disabled, etc.) (ID: TEST_A11Y)
Error Handling
Components should handle edge cases gracefully and provide clear error messages when props are invalid.
Examples
Complete Void Component
// Component.tsx
import React from 'react';
import { pipeline } from '../utils/pipeline';
import ButtonView from './View';
import type { ButtonProps } from './types';
/**
* Button component for primary user actions
*
* Supports multiple variants and states. Use primary variant
* for main actions, secondary for less important actions.
*
* @example
* <Button variant="primary" onClick={save}>Save</Button>
*/
function Button(props: ButtonProps) {
return <ButtonView {...props} />;
}
export default pipeline(React.memo)(Button);
// View.tsx
import { memo } from 'react';
import clsx from 'clsx';
import { pipeline } from '../utils/pipeline';
import type { ButtonProps } from './types';
function ButtonView({ variant = 'primary', disabled, children, onClick }: ButtonProps) {
return (
<button
className={clsx(
'void-button',
`void-button--${variant}`,
disabled && 'void-button--disabled'
)}
disabled={disabled}
onClick={onClick}
aria-disabled={disabled}
>
{children}
</button>
);
}
export default pipeline(memo)(ButtonView);
// Button.css
.void-button {
padding: var(--spacing-3) var(--spacing-5);
border-radius: var(--border-radius-md);
font-family: var(--font-family-base);
cursor: pointer;
border: none;
transition: all var(--transition-duration-fast) var(--transition-easing-ease);
}
.void-button--primary {
background-color: var(--color-brand-azure);
color: var(--color-base-white);
}
.void-button--disabled {
opacity: 0.5;
cursor: not-allowed;
}
// Button.stories.tsx
import type { Meta, StoryObj } from '@storybook/react';
import { Button } from './index';
import './Button.css';
const meta: Meta<typeof Button> = {
title: 'Void/Button',
component: Button,
tags: ['autodocs']
};
export default meta;
type Story = StoryObj<typeof Button>;
export const Primary: Story = {
args: {
variant: 'primary',
children: 'Button'
}
};
Related Skills
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
ui-ux-pro-max
130.2kUI/UX design intelligence for web, mobile, and desktop. This skill should be used when designing, building, reviewing, or fixing interfaces, including pages, components, design systems, accessibility, interaction, responsive layout, typography, color, charts, and stack-specific UI implementation.
design-is
94.6kAudit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign
dotnet-backend-patterns
39.9kMaster C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
