chore: update documentation for project guidelines and standards

[torleifhalseth]

No description provided.

[Copilot]

Pull request overview

This PR restructures and significantly expands the project's documentation guidelines to provide clearer, more actionable guidance for developers. The documentation is transformed from simple bullet-point lists into comprehensive, well-structured guides with concrete examples.

Key changes:

• Enhanced formatting with code examples demonstrating good and bad patterns
• Organized content into clear sections with visual hierarchy
• Added specific commands and practical instructions
• Standardized structure across all guideline documents

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
.github/instructions/ts.instructions.md	Expanded TypeScript guidelines with type definition patterns, functional programming principles, and comprehensive testing examples
.github/instructions/styling.instructions.md	Restructured CSS guidelines with BEM examples, responsive design patterns, and token usage
.github/instructions/react.instructions.md	Enhanced React component structure documentation with file organization, implementation patterns, and accessibility requirements
.github/instructions/global-coding.instructions.md	Improved global standards with formatted tables, practical commands, and clearer naming convention examples
.github/instructions/figma.instructions.md	Expanded Figma workflow with numbered steps, anti-patterns, and a checklist
.github/copilot-instructions.md	Simplified overview with streamlined package descriptions and guideline references

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.

[Copilot]

Missing semicolons in import statements. For consistency with TypeScript best practices, add semicolons after each import statement.

[Copilot]

Missing semicolons at the end of the export statement and function body. Add semicolons for consistency with TypeScript best practices.

[Copilot]

Missing semicolons in export and import examples. For consistency with TypeScript best practices, add semicolons after each statement.

Suggested change

	export const Button = () => {}
	export const useButton = () => {}
	// ❌ Avoid default exports
	export default Button
	// ✅ Import named exports
	import { Button, useButton } from '@equinor/eds-core-react'
	// ❌ Don't import default
	import Button from '@equinor/eds-core-react'
	export const Button = () => {};
	export const useButton = () => {};
	// ❌ Avoid default exports
	export default Button;
	// ✅ Import named exports
	import { Button, useButton } from '@equinor/eds-core-react';
	// ❌ Don't import default
	import Button from '@equinor/eds-core-react';

[Copilot]

The comment "No React import needed (no JSX pragma in modern React)" might be confusing. While it's true that React 17+ with the new JSX transform doesn't require importing React for JSX, the example code at lines 31-42 doesn't show any React import either. Consider clarifying this applies to JSX usage specifically, or show both cases (with and without JSX).

Suggested change

	- No React import needed (no JSX pragma in modern React)
	- For files using JSX with React 17+ and the new JSX transform, no React import is needed.
	For non-JSX usage (e.g., using React APIs directly), you still need to import React.
	Example (JSX, no import needed):
	```typescript
	// React 17+ with new JSX transform
	export const MyComponent = () => <div>Hello</div>;

Example (non-JSX, import needed):

import * as React from 'react';
// Using React.createElement directly
export const MyComponent = () => React.createElement('div', null, 'Hello');

[Copilot]

Missing semicolon at end of statement. For consistency with other examples in the documentation and TypeScript best practices, add a semicolon: const handleClick = (event: React.MouseEvent<HTMLButtonElement>) => {};

Suggested change

	const handleClick = (event: React.MouseEvent<HTMLButtonElement>) => {}
	const handleClick = (event: React.MouseEvent<HTMLButtonElement>) => {};

[Copilot]

Missing semicolon at end of statement. For consistency, add a semicolon: const handleClick = (event: any) => {};

Suggested change

	const handleClick = (event: any) => {}
	const handleClick = (event: any) => {};

[Copilot]

Missing semicolons in the test example. For consistency with TypeScript best practices, add semicolons after each statement.

[Copilot]

Missing semicolons in CSS property declarations. Add semicolons after each property for consistency.

[Copilot]

Missing semicolons in CSS property declarations. While CSS semicolons at the end of the last property in a block are optional, it's a best practice to include them for consistency and to prevent errors when adding new properties. Add semicolons after each property.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.