claudeguide-engineer 1.14.8

package/.claude/skills/frontend-development/resources/typescript-standards.md

@@ -0,0 +1,418 @@
+# TypeScript Standards
+
+TypeScript best practices for type safety and maintainability in React frontend code.
+
+---
+
+## Strict Mode
+
+### Configuration
+
+TypeScript strict mode is **enabled** in the project:
+
+```json
+// tsconfig.json
+{
+    "compilerOptions": {
+        "strict": true,
+        "noImplicitAny": true,
+        "strictNullChecks": true
+    }
+}
+```
+
+**This means:**
+- No implicit `any` types
+- Null/undefined must be handled explicitly
+- Type safety enforced
+
+---
+
+## No `any` Type
+
+### The Rule
+
+```typescript
+// ❌ NEVER use any
+function handleData(data: any) {
+    return data.something;
+}
+
+// ✅ Use specific types
+interface MyData {
+    something: string;
+}
+
+function handleData(data: MyData) {
+    return data.something;
+}
+
+// ✅ Or use unknown for truly unknown data
+function handleUnknown(data: unknown) {
+    if (typeof data === 'object' && data !== null && 'something' in data) {
+        return (data as MyData).something;
+    }
+}
+```
+
+**If you truly don't know the type:**
+- Use `unknown` (forces type checking)
+- Use type guards to narrow
+- Document why type is unknown
+
+---
+
+## Explicit Return Types
+
+### Function Return Types
+
+```typescript
+// ✅ CORRECT - Explicit return type
+function getUser(id: number): Promise<User> {
+    return apiClient.get(`/users/${id}`);
+}
+
+function calculateTotal(items: Item[]): number {
+    return items.reduce((sum, item) => sum + item.price, 0);
+}
+
+// ❌ AVOID - Implicit return type (less clear)
+function getUser(id: number) {
+    return apiClient.get(`/users/${id}`);
+}
+```
+
+### Component Return Types
+
+```typescript
+// React.FC already provides return type (ReactElement)
+export const MyComponent: React.FC<Props> = ({ prop }) => {
+    return <div>{prop}</div>;
+};
+
+// For custom hooks
+function useMyData(id: number): { data: Data; isLoading: boolean } {
+    const [data, setData] = useState<Data | null>(null);
+    const [isLoading, setIsLoading] = useState(true);
+
+    return { data: data!, isLoading };
+}
+```
+
+---
+
+## Type Imports
+
+### Use 'type' Keyword
+
+```typescript
+// ✅ CORRECT - Explicitly mark as type import
+import type { User } from '~types/user';
+import type { Post } from '~types/post';
+import type { SxProps, Theme } from '@mui/material';
+
+// ❌ AVOID - Mixed value and type imports
+import { User } from '~types/user';  // Unclear if type or value
+```
+
+**Benefits:**
+- Clearly separates types from values
+- Better tree-shaking
+- Prevents circular dependencies
+- TypeScript compiler optimization
+
+---
+
+## Component Prop Interfaces
+
+### Interface Pattern
+
+```typescript
+/**
+ * Props for MyComponent
+ */
+interface MyComponentProps {
+    /** The user ID to display */
+    userId: number;
+
+    /** Optional callback when action completes */
+    onComplete?: () => void;
+
+    /** Display mode for the component */
+    mode?: 'view' | 'edit';
+
+    /** Additional CSS classes */
+    className?: string;
+}
+
+export const MyComponent: React.FC<MyComponentProps> = ({
+    userId,
+    onComplete,
+    mode = 'view',  // Default value
+    className,
+}) => {
+    return <div>...</div>;
+};
+```
+
+**Key Points:**
+- Separate interface for props
+- JSDoc comments for each prop
+- Optional props use `?`
+- Provide defaults in destructuring
+
+### Props with Children
+
+```typescript
+interface ContainerProps {
+    children: React.ReactNode;
+    title: string;
+}
+
+// React.FC automatically includes children type, but be explicit
+export const Container: React.FC<ContainerProps> = ({ children, title }) => {
+    return (
+        <div>
+            <h2>{title}</h2>
+            {children}
+        </div>
+    );
+};
+```
+
+---
+
+## Utility Types
+
+### Partial<T>
+
+```typescript
+// Make all properties optional
+type UserUpdate = Partial<User>;
+
+function updateUser(id: number, updates: Partial<User>) {
+    // updates can have any subset of User properties
+}
+```
+
+### Pick<T, K>
+
+```typescript
+// Select specific properties
+type UserPreview = Pick<User, 'id' | 'name' | 'email'>;
+
+const preview: UserPreview = {
+    id: 1,
+    name: 'John',
+    email: 'john@example.com',
+    // Other User properties not allowed
+};
+```
+
+### Omit<T, K>
+
+```typescript
+// Exclude specific properties
+type UserWithoutPassword = Omit<User, 'password' | 'passwordHash'>;
+
+const publicUser: UserWithoutPassword = {
+    id: 1,
+    name: 'John',
+    email: 'john@example.com',
+    // password and passwordHash not allowed
+};
+```
+
+### Required<T>
+
+```typescript
+// Make all properties required
+type RequiredConfig = Required<Config>;  // All optional props become required
+```
+
+### Record<K, V>
+
+```typescript
+// Type-safe object/map
+const userMap: Record<string, User> = {
+    'user1': { id: 1, name: 'John' },
+    'user2': { id: 2, name: 'Jane' },
+};
+
+// For styles
+import type { SxProps, Theme } from '@mui/material';
+
+const styles: Record<string, SxProps<Theme>> = {
+    container: { p: 2 },
+    header: { mb: 1 },
+};
+```
+
+---
+
+## Type Guards
+
+### Basic Type Guards
+
+```typescript
+function isUser(data: unknown): data is User {
+    return (
+        typeof data === 'object' &&
+        data !== null &&
+        'id' in data &&
+        'name' in data
+    );
+}
+
+// Usage
+if (isUser(response)) {
+    console.log(response.name);  // TypeScript knows it's User
+}
+```
+
+### Discriminated Unions
+
+```typescript
+type LoadingState =
+    | { status: 'idle' }
+    | { status: 'loading' }
+    | { status: 'success'; data: Data }
+    | { status: 'error'; error: Error };
+
+function Component({ state }: { state: LoadingState }) {
+    // TypeScript narrows type based on status
+    if (state.status === 'success') {
+        return <Display data={state.data} />;  // data available here
+    }
+
+    if (state.status === 'error') {
+        return <Error error={state.error} />;  // error available here
+    }
+
+    return <Loading />;
+}
+```
+
+---
+
+## Generic Types
+
+### Generic Functions
+
+```typescript
+function getById<T>(items: T[], id: number): T | undefined {
+    return items.find(item => (item as any).id === id);
+}
+
+// Usage with type inference
+const users: User[] = [...];
+const user = getById(users, 123);  // Type: User | undefined
+```
+
+### Generic Components
+
+```typescript
+interface ListProps<T> {
+    items: T[];
+    renderItem: (item: T) => React.ReactNode;
+}
+
+export function List<T>({ items, renderItem }: ListProps<T>): React.ReactElement {
+    return (
+        <div>
+            {items.map((item, index) => (
+                <div key={index}>{renderItem(item)}</div>
+            ))}
+        </div>
+    );
+}
+
+// Usage
+<List<User>
+    items={users}
+    renderItem={(user) => <UserCard user={user} />}
+/>
+```
+
+---
+
+## Type Assertions (Use Sparingly)
+
+### When to Use
+
+```typescript
+// ✅ OK - When you know more than TypeScript
+const element = document.getElementById('my-element') as HTMLInputElement;
+const value = element.value;
+
+// ✅ OK - API response that you've validated
+const response = await api.getData();
+const user = response.data as User;  // You know the shape
+```
+
+### When NOT to Use
+
+```typescript
+// ❌ AVOID - Circumventing type safety
+const data = getData() as any;  // WRONG - defeats TypeScript
+
+// ❌ AVOID - Unsafe assertion
+const value = unknownValue as string;  // Might not actually be string
+```
+
+---
+
+## Null/Undefined Handling
+
+### Optional Chaining
+
+```typescript
+// ✅ CORRECT
+const name = user?.profile?.name;
+
+// Equivalent to:
+const name = user && user.profile && user.profile.name;
+```
+
+### Nullish Coalescing
+
+```typescript
+// ✅ CORRECT
+const displayName = user?.name ?? 'Anonymous';
+
+// Only uses default if null or undefined
+// (Different from || which triggers on '', 0, false)
+```
+
+### Non-Null Assertion (Use Carefully)
+
+```typescript
+// ✅ OK - When you're certain value exists
+const data = queryClient.getQueryData<Data>(['data'])!;
+
+// ⚠️ CAREFUL - Only use when you KNOW it's not null
+// Better to check explicitly:
+const data = queryClient.getQueryData<Data>(['data']);
+if (data) {
+    // Use data
+}
+```
+
+---
+
+## Summary
+
+**TypeScript Checklist:**
+- ✅ Strict mode enabled
+- ✅ No `any` type (use `unknown` if needed)
+- ✅ Explicit return types on functions
+- ✅ Use `import type` for type imports
+- ✅ JSDoc comments on prop interfaces
+- ✅ Utility types (Partial, Pick, Omit, Required, Record)
+- ✅ Type guards for narrowing
+- ✅ Optional chaining and nullish coalescing
+- ❌ Avoid type assertions unless necessary
+
+**See Also:**
+- [component-patterns.md](component-patterns.md) - Component typing
+- [data-fetching.md](data-fetching.md) - API typing

package/.claude/skills/google-adk-python/SKILL.md

@@ -0,0 +1,237 @@
+# Google ADK Python Skill
+
+You are an expert guide for Google's Agent Development Kit (ADK) Python - an open-source, code-first toolkit for building, evaluating, and deploying AI agents.
+
+## When to Use This Skill
+
+Use this skill when users need to:
+- Build AI agents with tool integration and orchestration capabilities
+- Create multi-agent systems with hierarchical coordination
+- Implement workflow agents (sequential, parallel, loop) for predictable pipelines
+- Integrate LLM-powered agents with Google Search, Code Execution, or custom tools
+- Deploy agents to Vertex AI Agent Engine, Cloud Run, or custom infrastructure
+- Evaluate and test agent performance systematically
+- Implement human-in-the-loop approval flows for tool execution
+
+## Core Concepts
+
+### Agent Types
+
+**LlmAgent**: LLM-powered agents capable of dynamic routing and adaptive behavior
+- Define with name, model, instruction, description, and tools
+- Supports sub-agents for delegation and coordination
+- Intelligent decision-making based on context
+
+**Workflow Agents**: Structured, predictable orchestration patterns
+- **SequentialAgent**: Execute agents in defined order
+- **ParallelAgent**: Run multiple agents concurrently
+- **LoopAgent**: Repeat execution with iteration logic
+
+**BaseAgent**: Foundation for custom agent implementations
+
+### Key Components
+
+**Tools Ecosystem**:
+- Pre-built tools (google_search, code_execution)
+- Custom Python functions as tools
+- OpenAPI specification integration
+- Tool confirmation flows for human approval
+
+**Multi-Agent Architecture**:
+- Hierarchical agent composition
+- Specialized agents for specific domains
+- Coordinator agents for delegation
+
+## Installation
+
+```bash
+# Stable release (recommended)
+pip install google-adk
+
+# Development version (latest features)
+pip install git+https://github.com/google/adk-python.git@main
+```
+
+## Implementation Patterns
+
+### Single Agent with Tools
+
+```python
+from google.adk.agents import LlmAgent
+from google.adk.tools import google_search
+
+agent = LlmAgent(
+    name="search_assistant",
+    model="gemini-2.5-flash",
+    instruction="You are a helpful assistant that searches the web for information.",
+    description="Search assistant for web queries",
+    tools=[google_search]
+)
+```
+
+### Multi-Agent System
+
+```python
+from google.adk.agents import LlmAgent
+
+# Specialized agents
+researcher = LlmAgent(
+    name="Researcher",
+    model="gemini-2.5-flash",
+    instruction="Research topics thoroughly using web search.",
+    tools=[google_search]
+)
+
+writer = LlmAgent(
+    name="Writer",
+    model="gemini-2.5-flash",
+    instruction="Write clear, engaging content based on research.",
+)
+
+# Coordinator agent
+coordinator = LlmAgent(
+    name="Coordinator",
+    model="gemini-2.5-flash",
+    instruction="Delegate tasks to researcher and writer agents.",
+    sub_agents=[researcher, writer]
+)
+```
+
+### Custom Tool Creation
+
+```python
+from google.adk.tools import Tool
+
+def calculate_sum(a: int, b: int) -> int:
+    """Calculate the sum of two numbers."""
+    return a + b
+
+# Convert function to tool
+sum_tool = Tool.from_function(calculate_sum)
+
+agent = LlmAgent(
+    name="calculator",
+    model="gemini-2.5-flash",
+    tools=[sum_tool]
+)
+```
+
+### Sequential Workflow
+
+```python
+from google.adk.agents import SequentialAgent
+
+workflow = SequentialAgent(
+    name="research_workflow",
+    agents=[researcher, summarizer, writer]
+)
+```
+
+### Parallel Workflow
+
+```python
+from google.adk.agents import ParallelAgent
+
+parallel_research = ParallelAgent(
+    name="parallel_research",
+    agents=[web_researcher, paper_researcher, expert_researcher]
+)
+```
+
+### Human-in-the-Loop
+
+```python
+from google.adk.tools import google_search
+
+# Tool with confirmation required
+agent = LlmAgent(
+    name="careful_searcher",
+    model="gemini-2.5-flash",
+    tools=[google_search],
+    tool_confirmation=True  # Requires approval before execution
+)
+```
+
+## Deployment Options
+
+### Cloud Run Deployment
+
+```bash
+# Containerize agent
+docker build -t my-agent .
+
+# Deploy to Cloud Run
+gcloud run deploy my-agent --image my-agent
+```
+
+### Vertex AI Agent Engine
+
+```python
+# Deploy to Vertex AI for scalable agent hosting
+# Integrates with Google Cloud's managed infrastructure
+```
+
+### Custom Infrastructure
+
+```python
+# Run agents locally or on custom servers
+# Full control over deployment environment
+```
+
+## Model Support
+
+**Optimized for Gemini**:
+- gemini-2.5-flash
+- gemini-2.5-pro
+- gemini-1.5-flash
+- gemini-1.5-pro
+
+**Model Agnostic**: While optimized for Gemini, ADK supports other LLM providers through standard APIs.
+
+## Best Practices
+
+1. **Code-First Philosophy**: Define agents in Python for version control, testing, and flexibility
+2. **Modular Design**: Create specialized agents for specific domains, compose into systems
+3. **Tool Integration**: Leverage pre-built tools, extend with custom functions
+4. **Evaluation**: Test agents systematically against test cases
+5. **Safety**: Implement confirmation flows for sensitive operations
+6. **Hierarchical Structure**: Use coordinator agents for complex multi-agent workflows
+7. **Workflow Selection**: Choose workflow agents for predictable pipelines, LLM agents for dynamic routing
+
+## Common Use Cases
+
+- **Research Assistants**: Web search + summarization + report generation
+- **Code Assistants**: Code execution + documentation + debugging
+- **Customer Support**: Query routing + knowledge base + escalation
+- **Content Creation**: Research + writing + editing pipelines
+- **Data Analysis**: Data fetching + processing + visualization
+- **Task Automation**: Multi-step workflows with conditional logic
+
+## Development UI
+
+ADK includes built-in interface for:
+- Testing agent behavior interactively
+- Debugging tool calls and responses
+- Evaluating agent performance
+- Iterating on agent design
+
+## Resources
+
+- GitHub: https://github.com/google/adk-python
+- Documentation: https://google.github.io/adk-docs/
+- llms.txt: https://raw.githubusercontent.com/google/adk-python/refs/heads/main/llms.txt
+
+## Implementation Workflow
+
+When implementing ADK-based agents:
+
+1. **Define Requirements**: Identify agent capabilities and tools needed
+2. **Choose Architecture**: Single agent, multi-agent, or workflow-based
+3. **Select Tools**: Pre-built, custom functions, or OpenAPI integrations
+4. **Implement Agents**: Create agent definitions with instructions and tools
+5. **Test Locally**: Use development UI for iteration
+6. **Add Evaluation**: Create test cases for systematic validation
+7. **Deploy**: Choose Cloud Run, Vertex AI, or custom infrastructure
+8. **Monitor**: Track agent performance and iterate
+
+Remember: ADK treats agent development like traditional software engineering - use version control, write tests, and follow engineering best practices.