typescript

TypeScript conventions and rules for Graph Explorer, including branded types, function style preferences, and type safety patterns.

1.00x

Quality

58%

Does it follow best practices?

Impact

85%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.kiro/skills/typescript/SKILL.md

TypeScript Conventions

General Rules

Do not change the VS Code setting typescript.autoClosingTags
Prefer named function syntax over anonymous arrow functions for module-level declarations (e.g., function handleClick() {} over const handleClick = () => {}). Arrow functions within function scope are fine.
Every commit should have no type errors
Use explicit type aliases instead of ReturnType<typeof ...> when available (e.g., use AppStore instead of ReturnType<typeof getAppStore>)

Branded Types

The project uses branded types from @/utils for type safety. These prevent accidental mixing of similar types at compile time.

Type	Creator Function	Location
`VertexId`	`createVertexId()`	`@/core/entities/vertex`
`VertexType`	`createVertexType()`	`@/core/entities/vertex`
`EdgeId`	`createEdgeId()`	`@/core/entities/edge`
`EdgeType`	`createEdgeType()`	`@/core/entities/edge`
`EdgeConnectionId`	`createEdgeConnectionId()`	`@/core/StateProvider/edgeConnectionId`
`ConfigurationId`	`createNewConfigurationId()`	`@/core/ConfigurationProvider/types`
`RenderedVertexId`	`toRenderedVertexId()`	`@/core/StateProvider/renderedEntities`
`RenderedEdgeId`	`toRenderedEdgeId()`	`@/core/StateProvider/renderedEntities`
`IriNamespace`	`splitIri()`	`@/utils/rdf`
`IriLocalValue`	`splitIri()`	`@/utils/rdf`
`RdfPrefix`	`generatePrefix()`	`@/utils/rdf`
`NormalizedIriNamespace`	`normalizeNamespace()`	`@/utils/rdf`

Always use the appropriate branded type instead of string when working with these identifiers.

Repository: aws/graph-explorer
Commit: 30587b0

Last updated: 5 days ago
Created: 5 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.